The new macro manager shows a list of buttons that contextually becomes enabled depending on the selected item. That's a very uncommon way to present functions and makes the UI noisy. It should be better realized per context menu with perhaps only the most important functions on the primary UI. I suggest New and Edit placed below the left treeview, and Run and Edit underneath the right.
I wanted to add a context menu in addition to buttons :D So, your suggestion will be strange: some actions will be available by buttons and other actions by context menu? If it's then I disagree
We have primary functions that are used most frequently and we have secondary with less importance. The UI should reflect this difference and provide access only the most relevant via heavy button control.
(In reply to Heiko Tietze from comment #2) > We have primary functions that are used most frequently and we have > secondary with less importance. The UI should reflect this difference and > provide access only the most relevant via heavy button control. But we have a place for all buttons right now, why we need to hide it? I just can't understand what's benefit ? Could you please draw some mockup for your suggestion?
Created attachment 197946 [details] buttons below How do we handle having only a 'New...' button for Basic when it could either be for a new module or a new dialog? The other macro languages don't have modules or dialogs so the 'New...' button under the left tree view would only be used to add a new library. One solution could be to show both a 'New Module...' and a 'New Dialog...' button when the selected entry in the tree is a Basic library. When the selected entry is the Basic language entry a 'New Library...' button could replace the 'New Module...' and 'New Dialog...' buttons. Another solution could be to have Module and Dialog radio buttons in the dialog that opens when the 'New...' button is pressed when the selected entry in the tree is a Basic library.
(In reply to Jim Raykowski from comment #4) > Created attachment 197946 [details] This is basically what I had in mind. > How do we handle having only a 'New...' button for Basic when it could > either be for a new module or a new dialog? Indeed, most items have no function at all associated. And Basic has three variants of New. One option could be a menu button "New >". Or we change the "New" button depending on the selection. But not really convincing. Another solution is to hide non-functional buttons - we have max three active. And these three could have enough space underneath the tree.
(In reply to Heiko Tietze from comment #0) > The new macro manager shows a list of buttons that contextually becomes > enabled depending on the selected item. ... and their function and label even changes. > I suggest New and Edit placed below the left treeview, and Run and Edit > underneath the right. How would this address the New-vs-Delete transmogrification? I would suggest we consider having button-ish widgets appear at the edge of the item's row in the tree view, when the item is selected, i.e. suppose Item 2 is selected; its line will look like +-----------------------------+ | Item 1 | | \- Item 2 X V | | Item 3 | +-----------------------------+ (ignoring the selection-coloration which I can't really do with ASCII graphics) and instead of X and V think of icon-based "buttons", in the sense of being pressable, not in the sense of looking like regular physical UI buttons. That would probably not cover all functions, e.g. "Organizer...", but it's something to consider.
Created attachment 198510 [details] Mockup We discussed the topic in the design meeting and came up with a similar customization as Eyal recommends.
(In reply to Heiko Tietze from comment #7) > Created attachment 198510 [details] > Mockup > > We discussed the topic in the design meeting and came up with a similar > customization as Eyal recommends. Let's delete all buttons then, why do we need it all in general? Are you sure dialog without any actions buttons is a good idea? Imagine new user wants to do something with a macro, he opens the dialog, he see macro and nothing more >_< He may be will try a double-click for macro running, but I don't think he will think about context menu...
Sorry for not adding a detailed explanation: the selected node has buttons for the most frequently needed function inline (in the example for New and Edit). All functions are available per context menu including those in the primary UI.