Sorry Mook, but I’ve got to disagree.
The command dialog is really not that complex or intimidating. Look at preferences. If that’s acceptable to Komodo’s target audience, I really can’t see how a confirm check box in command properties would throw them for a loop. A confirm check box is pretty much as simple an addition as could be made and would greatly enhance the utility for those who support a team of programmers or a classroom of students. Or even those who just would like to make their personal irreversible commands safer, especially in toolbars, where a single misplaced click can invoke the command. This seems like a very good addition to me, well worth the extremely small addition to complexity.
As for beginners, fine, they need extra hand holding always. But they can do what beginners always do. Ignore any setting they don’t understand or care about, and let the default (unchecked) be. As for professional programmers, professors and college students, which I assume is the bulk of your audience, I hardly see this as an issue.
As for using the macros to do this simple but very important task, ouch! Talk about adding complexity! So, to get a confirm box:
- Make the command in some toolbox folder that is not the toolbar.
- Record a macro accessing that command, save it in the toolbar.
- Edit the macro to present a confirm dialog. (Exactly how do I access
Komodo’s confirm dialog? Please don’t say I should ‘manipulate the
- Return on cancel, or run the command on ok.
So, every time I want to make a command that should be confirmed, I need to maintain a separate folder for the command, give the command a non-clashing name, record and modify a macro for the toolbar, have a fragile link to maintain. I’d much rather just check a confirm check box in the properties.
The purpose of an IDE is to make my life easier, not more complex. All this complexity is added by trying to add the functionality of confirmation in the wrong place… the macro. It see seems fairly obvious to me that it is a property of the command and therefore belongs in the properties dialog. Talk about DRY, that’s the place it can be implemented once for reuse.
Macros are for doing things above and beyond the reasonable support the IDE offers like particular group needs, particular programmer needs, particular project needs. I’m very happy to go through the hoops to do something that isn’t something is so basic, so clearly a property that is needed, has such wide application for a wide group of users and improves the usability and safety of the IDE so much.
Sorry, Mook, I misunderstood your directions. I just tried recording the command from the tool menu run command. Before, I was recording the macro by clicking the existing command from the toolbox itself. The tools run command macro doesn’t find the part, so no need to maintain a separate part and a macro to invoke it. It actually demonstrates how to make a command call directly.
So, the amount of complexity in creating the commands is much less than I asserted above. I’d still like my pony, but if someone can show me how to invoke and act on a Komodo confirm dialog, I would be quiet about this feature from now on.