Mark Fletcher wrote: > I was a bit dismayed to find that "confirm" cancels execution not just > of its parent command, but also of all commands all the way up the > chain. So, no matter how much you modularize your commands, if a user > clicks "No" in some subcommand, all processing stops. > > Are there any other options for showing a simple OK/Cancel dialog that > would act more like a test expression than as an "exit" command? > > If not, it would be very helpful to have a few different scope levels > of "confirm": > > * sequence level - where confirm would act just like a "test" > expression, to allow a user to cancel the execution of a sequence. > * command level - where confirm would cancel execution of its parent > command only > * global level - where confirm would behave the way it does now, ie. > all processing stops. > > What do you think? Is any of this possible?
Everything is possible if you write your own prompt commands in Java[tm]. Please consider the problem you describe as a limitation of XXE's macros. We do not intend to enhance XXE's macros because we think we have found a good balance between power and simplicity. We intend to support JavaScript[tm] as an alternate, less intimidating than Java[tm], way to write commands, document hooks, etc. Don't hold your breath, this feature is pretty low on our TO DO list. However it's definitely on our TO DO list and we are committed to implement it.
