On Sun, 17 Jul 2011 11:08:17 -0500 "Edward K. Ream" <[email protected]> wrote:
> On Sun, Jul 10, 2011 at 6:38 PM, Terry Brown <[email protected]> wrote: > > Just a heads up that I've fiddled with the doubleclick handling code on > > the trunk, please let me know asap if anything seems odd. > > [snip] > > > however it didn't fix the problem I was trying to fix, namely that > > doubleclicks which open new outlines also start editing in the source > > outline and leave the focus there. If you start typing in the new > > visible outline your actually trashing the headline in the now obscured > > source outline. Possibly only in qttabs, the window switch may avoid > > the problem in the non-tab gui. > > I'm going to look into this next. This is pretty important code, and > I don't want to use the timer solution if it can be avoided. Great - you asked if I tried c.endEditing() in the old c - no, didn't know about it and haven't gotten to it since. My untested thoughts are that (a) a c.doubleClickFlag approach might work, I think that was done for Tk, and (b) even better would be to set up the execution path so the ‘icondclick1’ hook can stop execution flowing through to edit mode. I noticed in some places code read: g.doHook('some-hook1') c.doWhatever() g.doHook('some-hook2') When I think, according to the yeses in the table at http://webpages.charter.net/edreamleo/scripting.html#event-handlers it should be if g.doHook('some-hook1') is None: c.doWhatever() g.doHook('some-hook2') I fixed that for ‘icondclick1’ but you might want to check the rest. Even though I fixed that, control was still reaching the editing code. Cheers -Terry > Edward > -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/leo-editor?hl=en.
