Thank you both for your responses. I'm not sure I'm cheating but sometimes it feels like it. My plug-in is a floating search/replace (but only replaces) window. It seems ideal for me to only create one of these windows per instance of Leo (not per commander). I want replace history to be shared by all commanders and I'm currently doing that with object state. I am interested in "the commander that the user is currently looking at", so perhaps g.app.log.c will work fine for me. I haven't encountered any problem since I began using it (rather it solved the issue I was dealing with).
When I release the plugin I will hopefully get a better idea of if this design decision will be an issue. On Sunday, July 12, 2015 at 3:12:55 PM UTC-4, Edward K. Ream wrote: > > On Sat, Jul 11, 2015 at 12:18 PM, 'Terry Brown' via leo-editor < > [email protected] <javascript:>> wrote: > >> >> The use case for wanting to know "the commander the user's currently >> looking at" is an external input to Leo (remote procedure call kind of >> thing, from leoserver.py or mod_http.py etc.). >> > > In that case, the original answer should work: g.app.log.c. > > As long as all your >> >> commanders are in the one tabbed ui, the answer is "the commander for >> >> whatever tab is currently active", I'm not sure what the path to that >> >> is. >> > > Me neither, but g.app.log.c should be equal to it :-) > > > EKR > -- 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/d/optout.
