I love the DCL-string formatting you did, do you use some snippet for this?
I write DCL code in the Visual LISP IDE, and use the same to convert to string format simply using the various find/replace/prefix/append options offered by the IDE.
Because I think about writing some (in case you did this by hand).
BTW, Nice thread! (sorry for the offtopic)
You may get some ideas from this old program: Format DCL
On the contrary - since these tiles have predefined action statements, you can exploit this to avoid the need to define action_tile expressions for your tiles:Now I know that:
Just like roy_043 mentioned.
is_default; equals to (action_tile "accept" "(done_dialog 1)")
is_cancel; equals to (action_tile "cancel" "(done_dialog 0)")
Not quite: this equivalence is only applicable to the is_cancel
attribute; the is_default
attribute will only set the tile as the default and will not assign an action - if in doubt, simply include the tile keys.
Are you saying that (done_dialog) is not allowed in an action attribute? That seems strange.
Note that this is not valid in AutoCAD; also, the action attribute value will only be evaluated for tiles with keys.
Provided a tile has either the is_default or is_cancel attribute...An action attribute defined in the DCL that includes (done_dialog) also works.
is a perfectly valid action attribute value in AutoCAD, however, I was asserting that the action expression will only be evaluated for tiles with keys (per Grrr1337 above). Also, that this action expression alone is not sufficient for a valid DCL GUI: the tile must also have either an is_cancel
attribute (else AutoCAD will complain that the GUI has no OK or Cancel button).