|
|
On 5/21/21 9:57 PM Ian MacArthur wrote:
On 21 May 2021, at 13:11, Albrecht Schlosser wrote:
I'd also like to see an option to switch drivers (GDI <-> GDI+) dynamically so users can maybe switch back to pure old GDI in time-critical drawing paths (somebody mentioned this, IIRC). This option might already exist (internally) but I don't know if there's an API to be easily applied. If so, it should be documented.
I have no idea if this is even feasible?
We’ve never really had support for changing the back-end dynamically at runtime, though, have we? It’s always been a build-time sort of option.
Changing the "driver" during runtime is well-established. Think of
offline drawing, Fl_Printer, and whatnot.
Changing the rendering mechanism dynamically at runtime might be quite cool though (not just for this, but in general) but it sounds like quite a challenge.
The difference here would be that we change the drawing context, not the
device per se (i.e. we're still drawing to the display). This might
indeed be more involved, but Manolo said already that he would try it.
Looking forward to his results.
--
You received this message because you are subscribed to the Google Groups "fltk.coredev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to fltkcoredev+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/fltkcoredev/e326ce3b-f490-8a6e-8d4d-2c41d7886a5b%40online.de.
[ Direct Link to Message ] | |
|
| |