Take your time,. i just realized I had a bug with the setting of the scrolling position , and the selected selection range , which are crucial in the next feature to implement before release of leointeg 1.0 : "search in outline" ctrl+f, f2, f3. etc.. gonna fix this tonight and or tomorrow.
(other than making leoserver work as much as leobridgeserver so to replace it completely) -- Félix On Tuesday, May 18, 2021 at 10:10:12 AM UTC-4 Edward K. Ream wrote: > On Mon, May 17, 2021 at 6:31 PM Félix <[email protected]> wrote: > >> Thank you - but oh no! -> the bug still remains ! > > > Oops. I have just created #1946 > <https://github.com/leo-editor/leo-editor/issues/1946>: Ensure that Qt > plugins call g.assertUI('qt'). > > I expect to complete work on this issue later today. > > The recent bug happens because I mistakenly removed the call to > g.assertUi('qt'). This call raises g.UiTypeException if g.app.gui is not > the Qt gui. The plugins manager catches this exception. > > Imo, it's better to use g.assertUI than to create top-level if statements > that guard class definitions. > > There will be two parts to the fix: > > 1. Call g.assertUI('qt') in all "real" Qt plugins, as follows: > > # > # Fail fast, right after all imports. > g.assertUi('qt') # May raise g.UiTypeException, caught by the plugins > manager. > > 2. Write a unit test that ensures that all qt plugins raise > UiTypeException when using a Null gui. > > 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/c3bdcfb5-6700-4e3f-9fe6-9e4fd7cd6226n%40googlegroups.com.
