In all the years I never used this setting. Even if the name says "margins" it was "clear" to me from the beginning that this is the setting for the default size of the frames in a new application. I never scrutinized that. The standard values are 640x480 just like the standard frame size. I find these standard values really confusing. Maybe it's a programmer thing? What does it mean? 320 pixels to the left and right and 240 pixels to the top and bottom? Maybe other starting values would be less confusing.
I found another small issue.
If you double-click on the info box (which contains the actions when you hover over a check mark in the Event Editor) you can edit actions directly.
Sometimes this doesn't work. I tried to isolate it...
It doesn't work if you create a new application, go to the Event Editor, create a condition and an action for the first time the Event Editor is opened.
Changing to another window and going back to the Event Editor fixes this issue. This also counts for the following cases below.
In already existing and freshly loaded applications it shows the following behavior:
- It works directly if you change nothing.
- It works if you drag&drop an existing condition as a new one and if you drag&drop an existing action in this new line.
- It doesn't work if you drag&drop an existing condition as a new one and if you create a new action.
- It doesn't work if you create a new condition via popup and if you drag&drop an existing action in this new line or create a new action.
Conclusion: As soon as you insert a new condition or action the first time you opened the Event Editor it doesn't work anymore, even if it worked before. But if you change to another window and back to Event Editor it works as expected.
Now it occurred more often even after switching back to the Frame Editor.
But after one quick change again back to the Frame Editor it works again.
Must have something to do with the editing of actions.
I would also like to talk about some UX cases.
The new Toggle Event List mode command is really useful but has one big downside.
It clutters the navigation history (Back & Forward buttons in toolbar). Every time I press the toggle button or use Ctrl+T a new navigation entry is added.
In my opinion this circumstance makes the navigation obsolete if I use the toggle button frequently. To go back to the window before, I have to press Back as many times I toggled the windows.
Of course I can press the Back button after using the toggle button but if I do so: what would be the point of the toggle button? So I could use the other editor buttons right away.
So maybe it's a better idea to exclude the toggle button from the navigation history. But that could be confusing too.
A possible solution could be to add an entry in the navigation history only if the window Fusion would jump to is different from the second last history entry (Event Editor or Event List Editor).
I don't know if I described it okay. Let's say the following list represents the navigation history, the newest entry at the bottom:
- Storyboard Editor
- Frame Editor
- Event Editor
If I press the toggle button now an entry Event List Editor will be added at the end. If I press it again Fusion finds that the second last entry is Event Editor so it doesn't add it again to the end. It just deletes the last entry Event List Editor. Now I can press the Back button and jump back directly to the Frame Editor.
I think this would be a plausible solution because the toggle button is different from all other editor buttons and visually represented as "option/check" which changes appearance when in Event List Editor.
Speaking of navigation history, there is a small issue. As far as I can see the Storyboard Editor button is the only one which keeps adding entries to the navigation history every time it's pressed. Press it ten times in a row and ten entries will be added.
Another UX case is the option to open the Expression Editor via keyboard.
I like to work with the keyboard as much as possible and there are some really essential "shortcuts" missing in my opinion.
In the Frame Editor, Frame List Editor and Action Editor one is able to move the selection mark with the arrow keys. One can copy, cut and paste and select conditions and actions (via spacebar) using the keyboard. But it is impossible to open the Expression Editor of an existing action for example. I always have to take my mouse, move it over the action and double-click on it. After editing an action I move intuitively the selection mark by pressing the arrow keys to the next action I want to edit and press Enter - but nothing happens. Often I just have to change a value and close the Expression Editor again using Enter. But this "flow" is interrupted by the missing option to open the Expression Editor with the Enter key.
It would be really helpful if one would be able to press Enter to:
- open Expression Editor for Actions
- open Expression Editor for Conditions
- activate the New condition button
Puh... that's all for now. Thank you
many ways you can improve your Fusion experience with Autohotkey.