temaran / feather Goto Github PK

The relationship between window style and window is not good. This stems from the fact that AS supports neither Delegates, nor Interfaces. If we had delegates then the style could expose delegates for stuff like Resize. Events won't work since they cannot return the needed EventReply. If AS had proper interfaces, we could make an IFeatherWindow that could hold the necessary methods. But since interfaces in AS are essentially base classes, and we want window to derive from UFeatherWidget, that doesn't work either.

Almost all bugs so far has been in relation to serialization; When to save and what to save.

Since we have so many objects that are dynamically added, serialization feels messy. I think it's in a fairly good state now, but I can't help but think that there might be a better solution.

Having to define UFUNCTION overrides in intermediate classes is annoying as always in AS. I think this comes from Blueprint, but patching AS to automatically generate these UFUNCTION stubs when they are needed would make base class code so much cleaner.

I want to be able to sort the entries in the search result panel, but if I readd them, the widgets reset, and there is no way to just change their index in the panel. Maybe adding a bind could fix it?

Sorting in AS is very limited and having to implement my own quicksort is not great. This feels like a fairly high prio thing to fix. Normally, I would implement the sorting method in cpp and leave it at that, but forcing the project to AS only of course blocks me from using that strategy. See sorting files for more details.

A general problem with AS is that if you build shipping but don't nativize, preprocessors like #if RELEASE really do nothing as script is simply copied verbatim to the output. For the uncareful, this could lead to debug code leaking into releases. Would be great if the AS cooker would actually process #if preprocessors and stripped code that doesn't pass.