I won't argue. I will just emphasize that there is some difference between pyqt6.03 and 6.11 in terms of compatibility, and who knows which one users will have installed.
On Wednesday, July 7, 2021 at 10:41:16 AM UTC-4 Edward K. Ream wrote: > On Tue, Jul 6, 2021 at 5:31 PM [email protected] <[email protected]> > wrote: > >> Last time I tried it with *devel*, Leo wouldn't even run with the latest >> version of pyqt6 (6.11). And even if it will by now, some plugins probably >> won't work correctly or at all. So I'm inclined to say not to worry about >> it at this preliminary release (pre-6.4 final), and not to make it a major >> goal. If it turns out to happen, fine. With VR3, rendering will be >> crippled until we get the new equivalent of webEngineView, possibly in the >> fall. Freewin will be in better shape but still won't do the rendered view >> well but you don't need it to use the plugin). > > > Thanks for these comments. They helped me think about my options. > > After some thought, I would like to fix the pyQt options for b1. That will > allow us all to test the new code. > > I don't want to mess with a new command-line option. I would just have to > remove it later. > > 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/6a89da84-d0be-49a3-9102-e58997e773d3n%40googlegroups.com.
