For occasions when keypress means something apart from the expected default action (this doesn't mean commands, they can be handled by QAction/QShortcut), you would have a dispatch dict that calls your own function. This would be in the ui layer as well, not core.
Core needs to be asked for what the completions are, not how user activates them. ----- Original message ----- > > > On May 13, 5:29 pm, Terry Brown <[email protected]> wrote: > > On Thu, 13 May 2010 14:07:13 -0700 (PDT) > > > > tfer <[email protected]> wrote: > > > Well, I still really like the ability to put a hook in between the > > > keypress and the printing into what ever widget is the target, there > > > is just too much interesting things that makes doable that a strict > > > lock-in would make impossible. > > > > I don't think that possibility is being excluded, I think it's just a > > matter of whether that kind of code's in the core or in a module which > > sits between the core and the gui, effectively extending the gui. > > > Yeah, I can see that from Ville's comment, My post crossed with that > on this threads time-line. > > > I can't remember whether it's you or someone else whose pursuing the > > vi emulation, but when does that need to interact with leo beyond the > > "here's the new body text" level? That's a question, not a implied > > suggestion that it doesn't, BTW :-) > > While I'm interested in the Vi/Vim stuff, I'm not working on that, I > have more interest in a IPC interface between Leo and Vim so Vim could > act directly as the editor component, opening buffers in accordance > with navigation in the Leo outline pane. > > The use case I'm looking at the needs to have the ability to sometime > sit between the key-press and the target widget, have to do with all > the auto-completion stuff. There are times when tab has several > different possibilities, e.g. insert a tab, insert spaces equivalent > to a tab, find the 'trigger' to the left of the insertion point and > offer up the first suggestion, offer up the next suggestion, drop down > a list of possible completions/expansions, offer up a number/lettered > list of possible completions/expansions that can be selected from by > typing the number/letter associated with the desired choice, move to > the next 'tabstop', (blank), in an inserted template -- then taking > characters entered to fill in that tabstop, or if optional and tabbed > past it, deleting that stop and advancing to the next tabstop. > > Tom > > -- > 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. > -- 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.
