On Sat, 28 Sep 2013 07:09:26 -0500 "Edward K. Ream" <[email protected]> wrote:
> Done at rev 6074. To emphasize what is said below in the checkin log, > there is a systemic problem with the leoBridge module: it uses a nullGui in > which all dialogs are do-nothings. This will affect all commands, such as > c.save, etc., that may (or may not) ask the user for input. Ah, makes sense now you point it out - tricky. Explicit filename's ok for saveAs, a more general solution is hard to imagine. If all dialogs flowed through a single execution pathway / wrapper, you might be able to use something like: c.pushDialogResult(someResult) c.functionUsingADialog() # null gui returns someResult - maybe a common execution pathway / wrapper for dialogs isn't critical, this could be part of the implementation of the nullGui dialogs. - how many cases are we really talking about? I can't think of any others beyond saveAs. I guess there's a bunch of save<somethings> Cheers -Terry -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/leo-editor. For more options, visit https://groups.google.com/groups/opt_out.
