Hi Stu, A lot of the code seems to be glue to match up the methods. It doesn't seem like there is any way around it, because the pyglet methods need to be called in order to update some internal things, in this case by the coresponding QT methods. The dummy context is Since it's so specific, It wouldn't make much sense to include this inside the main pyglet codebase. It might be useful to have this type of shim code in the /contrib folder on BitBucket, however, if someone wants to write and contribute it.
On Friday, August 18, 2017 at 8:58:30 AM UTC+9, Stu.Axon wrote: > > Hi, > I wonder if Window could be changed to make embedding it in Qt, Gtk or > anything that has an existing GL context easier. > > I looked at how QPygletWidget [1] works, and a fair bit it seems to be > mocks and stubs. > > Are there any changes that could be made on pyglets end to make these > stubs and workarounds unnecessary ? > > > [1] QPygletWidget by ColinDuquesnoy > > https://github.com/ColinDuquesnoy/QPygletWidget/blob/master/qpygletwidget.py > > -- You received this message because you are subscribed to the Google Groups "pyglet-users" 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 https://groups.google.com/group/pyglet-users. For more options, visit https://groups.google.com/d/optout.
