Thank you!
- Duplication is currently only enabled for resources where it’s safe to do so - otherwise it increases maintenance cost (read: time I have to spend verifying that everything still works without breaking projects after each GM update)
- Perhaps at a later time - Drag ‘n Drop is currently used for opening files in GMEdit, so it’d be strange to have this add resources for some file types
- You can symlink (
mklink
/ln
) an image to its source; you could probably butcher AseSync to watch and copy non-Aseprite PNGs. - My fork of builder has an option for that.
- I’m not sure what this means.
- This is a broader issue with manipulating resources without reloading - I need to refactor some code (previously GMEdit simply re-indexed the project after such operations like IDE does, but people complained that this is slow on huge projects - just like the IDE’s operations).
@desc
is cursed and is misused even by the GMS2’s own project importer.- Perhaps - I’ve not settled on a good way of handling this and Global Search popups yet.
- I could use an example.
- You can set initial size in preferences. I do not currently attempt to re-position the window since Electron applications are prone to opening completely off-screen (there are no safety measures in place and Windows will just let you).
- You can do this in a custom theme -
#outline-view .outline-current-file
,#outline-view .treeview > div
. - I could use a GIF or clearer reproduction steps.
- My aforementioned fork of Builder has a “Fork aside” option, which will scroll. Due to how Ace works, code isn’t inherently aware of additional “viewers” unless you do some hacky things.
- I could use a specific example.
- It is a simple red flash because custom themes may feature arbitrary colors.
- Treeview ultimately needs to be replaced by a better-suited component with dragging-dropping, multi-selection, and so on, but doing so requires a lot of rewriting and will break themes.
- see above
- Not sure what this means.
- Room Creation Codes are currently somewhat hackily supported based on someone’s one-off request - they aren’t resources in conventional sense, so the editor doesn’t know how to open a specific one (and instead asks the system to open it)
- Indexer currently isn’t smart enough to figure out whether you are calling the said function during creation or not - using a script with
@interface
+@implements
is an alternative. - It does, but I’ve not yet found a good way to handle this that doesn’t require each theme to set its own (opaque) warning/error line backgrounds. “in the wild” Ace editor uses seem to mostly settle for not giving warning/error lines backgrounds.
- I could use a specific example+settings - no scrollbars should appear outside of treeview/file/Outline views.