Printable View
The new feature that lets you scroll the Event List Editor with MMB is great. But it also breaks things if you do it to a frame with few visible events (either because most events are in closed groups, or because it doesn't have many events in it in the first place). For example, create a new MFA, press MMB, and this happens:
https://bit.ly/3DOSH6h
Everytime i try to edit the about text and hit save, it is modified by a chain of numbers instead, even if i let it blank:
Attachment 30518
This is caused by SteamWorks object, no idea why it does this, Yves also doesn't know, it can't be fixed without modifying the extension with its source code.Quote:
Originally Posted by Dobermann
Could we please get a few actions to set the state of "Resize display to fill window size", "Fit inside (black bars)" and "Anti-aliasing when resizing"?
It would help a lot to make full screen apps that adapt to any aspect ratio.
But, for windowed mode, it would also be nice if it was possible for "Adjust frame size" to affect it, and if possible fullscreen mode as well.
This way toggling the options wouldn't be necessary, but would still be useful for customization purposes.
"Anti-aliasing when resizing" was added a few builds back, but I agree it would be nice with more of these options as actions during runtime.Quote:
Originally Posted by NaitorStudios
If you use Invert Selection and try copying, cutting or deleting, it will only affect the original selection, not the current one.
This means Invert Selection option is just working visually but not functionally.
1. Could we get a hint of the comment which is above the "on loop/on each/on timer" condition when mouse hover on a "start loop/start loop for-each/fire event" action? (like you hover on a function and VS give you the hint)
It will be super handy when working with a long term big project (that is to say, it's almost impossible to remember what each loop will do in this case), and user need not to double-click the action, copy the loop name, then paste it to find all, and jump to the "on loop" condition by clickting results in the find toolbar to find what the loop actually is (or which event is calling it).
2.if the first one is hard to implement, is it possible to add a "quick find all" feature? e.g. pressing ctrl and click on an condition/action, fusion will trigger a search based on this condition/action, especially for loops.
The Event Explorer forgets its state between sessions, and all groups are reclosed when you reload an MFA. I think it would be good if it remembered which groups were open/closed, the way the editors do. I don't know how easy this would be to do though. Since the Event Explorer is a 2.5+ feature, I guess you'd have to save information into the MFA in a way that was successfully ignored by 2.5 builds.
Is it possible to have tooltips on the Find All window that show the entire text of the line?
The Find All Window usually needs a lot of vertical space so you can easily scroll through many lines. But it also needs lots of horizontal space because the entries are so long (wide). I actually have about 2/3 of a whole monitor devoted to the Find All window (the other 1/3 is the workspace toolbar). Yet even so it's still rarely enough to see the entries properly. Below, for example, I can't tell which events are setting my flag to on and which to off. I think a tooltip would solve this pretty well.
https://bit.ly/2X71lw2
You could potentially shorten some of those entries too. There's a ton of repetitive information on the left that often pushes the more specific information out of the panel:
-"Event line #1234" can be shortened to "Event #1234" or "Line #1234"
-I don't think "Frame events" is necessary, since the line already begins with "(Frame)" and the name of the frame
-I personally don't see how it's useful to see whether an action is "action #3" or "action #79". Clicking on the entry highlights the action for me, so I don't need to know what number it is.
-You could perhaps have a simple legend at the bottom and use initials or symbols for some of the terms, like F for Frame, E for Event Line, A for Action
-There are a few extra spaces that you could remove before/after various colons
ExampleObbFull
When build apk : ErrorLog.$$$
Attachment 30533