On Fri, 15 May 2020 at 10:48, Austin Green <austin.gr...@orcon.net.nz> wrote: > > Hi Matthew, > > On Thu, 14 May 2020 16:20:58 -0700 > Matthew Brush <mbr...@codebrainz.ca> wrote: > > > Can you elaborate on what you are trying to do specifically? There may > > be a better way. > > Sure thing. > > The plugin 'recordkey', and possibly others, connects to the > 'key-press-event' signal. Possibly depending on the order of plugins being > loaded, or possibly not, but either way: some of the keys bound to other > plugins are lost to the view of 'recordkey', presumably because Geany > processes all of the keybindings in its handling of the 'key-press-event' > signal. The order of loading plugins cannot be controlled anyway, as the > user may load/unload at any time. Causing Geany to emit a new signal, on > receipt of the 'key-press-event' signal, but prior to any processing, allows > any plugin (that connects to the new signal) to view (but not suppress) all > key press events.
Of course you can't enforce non-suppression, the best you can do is to document it clearly (hint not to forget the documentation :) > > I'll be pleased if there is another way which doesn't involve changing Geany, > it will save me some work. ;) And of course it's always good not to have > to bump the ABI version. I think a new signal that doesn't change the semantics of any other signal or function probably won't need ABI just API version change Cheers Lex > > Cheers, > Austin. > _______________________________________________ > Devel mailing list > Devel@lists.geany.org > https://lists.geany.org/cgi-bin/mailman/listinfo/devel _______________________________________________ Devel mailing list Devel@lists.geany.org https://lists.geany.org/cgi-bin/mailman/listinfo/devel
