|
|
On Sunday, 31 July 2022 at 22:20:37 UTC+1 jacky... wrote:
I'm considering FLTK to build an emulator frontend for Mupen64Plus.
To allow the emulator to provide output, it needs a (child) window that it gains exclusive control of. This means that I need to somehow disable calling swap_buffers() after draw() in an Fl_Gl_Window, so that I can manually call swap_buffers when I desire.
However, I only want to do this for the emulator's child window. I want everything else to draw according to FLTK's event loop.
How would I accomplish this?
This sounds a lot like a GL question - so not exactly my area!
However, I think if you derive your own window widget from Fl_GL_Window, for use as your child window, and in the implementation of that derived widget you DO NOT call the base class draw or event handling, then the derived window will not get any swap_buffer events unless you explicitly trigger them.
But... do not take my word for it, I may be talking nonsense...
--
You received this message because you are subscribed to the Google Groups "fltk.general" group.
To unsubscribe from this group and stop receiving emails from it, send an email to fltkgeneral+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/fltkgeneral/66b409c4-1bac-4228-b5bf-1a932d8c6a8bn%40googlegroups.com.
[ Direct Link to Message ] | |
|
| |