Perhaps I should have made more research before asking about those things but i'll ask anyways - sorry in advance if this is basic stuff... (multiple opened file support is the last major feature of leointeg to be done, the rest is trivial... So i'm tempted to ask questions instead of studying the problem for a longer time because i'm eager to finish! )
I've made sure to comment out my override of g.app.commanders in the __init__ of LeoBridgeIntegController. and then, I start my 'openFile' method in leobridgeserver.py as usual, but I added a printout of the g.app.commanders this way: def openFile(self, p_file): '''Open a leo file via leoBridge controller, or create a new document if empty string''' self.commander = self.bridge.openLeoFile(p_file) # create self.commander # did this add ato existing array of g.app.commanders() ? print(str(self.g.app.commanders())) # test *but the print outputs an empty array : [ ]... !* I'm still trying to untangle the concepts of window, frame, commander ... they're all somewhat synonyms in my mind : "an opened Leo document" so its taking me a long time hehe.. also trying to get a good grip of what are 'containing/pointing to' those things. I'm also trying to figure out if files opened via leoBridge would still fill up this array, and also i'm trying to figure out if when starting a bridge like this: self.bridge = leoBridge.controller( blabla.... ) does this open up all the 'current / recent) leo files that opening normal leo would and place the controllers of all those leo files visible in g.app.commanders() ? -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/leo-editor/3bbb74b6-a6ac-4e47-88ae-d09cc4dc509do%40googlegroups.com.
