On Sun, Sep 27, 2020 at 3:15 PM Félix <[email protected]> wrote:
[The problem is] that methods in Leo (such as getScript in leoGlobals.py) > consider important to check if they're in leoBridge (!), even if they also > check if the wrapper is available on the frame.body ! (see line 14 of > getScript in leoGlobals.py) > It's possible that g.getScript has this weird check because of the console gui. wadaya think? > Perhaps I misunderstood you. The general idea was to leave Leo's core unchanged, but call it with g.app.inBridge = False. That's all the wrapper does. How general is the problem? If it's only a few methods/functions, the patching technique I discussed could be used to patch g.getScript (and any other pesky methods/functions) to your liking. Edward -- 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/CAMF8tS32qqmFsmcFFDw5keEkGX3r-KOALt0TX3Y6kWuBS97_iA%40mail.gmail.com.
