Re: Towards a Wayland platform for the FLTK library ?
Bill Spitzak
Jun 07, 2021
What I meant for Device was to replace it with code like this:
#if X11
#include <X11code.C>
#elif Windows
#include <Windowscode.C>
...
This is what was attempted in FLTK 2.
This should result in something exactly as maintainable as Device virtual functions, but there is no overhead and mistakes show up as unlinkable code.
It may be plausible to use Device to make a program that works on different devices but a lot of stuff, in particular timeouts and polling, are in it and there is just no way you can switch that to a different one.
On 7 Jun 2021, at 20:03, Albrecht Schlosser wrote:
>
> I used a VM (Ubuntu) where I had installed Wayland some time ago for tests. Almost all programs run fine and smoothly.
> test/glpuzzle does "funny things" (TM) if you let the game rotate (drag the mouse and see). Borders disappear, sometime there's a see-through effect.
I would not preclude the possibility that the VM is involved in that misbehaviour - I was doing some testing on (IIRC Fedora) VM and the GL rendering was a bit glitchy.
The same binary running native on another machine was fine.
(The Fedora VM was because the end-user was on RHEL-something-or-other and I was working on debian, so I just wanted to see what happened on something more RHEL-like. The GL misbehaviour caused me some distress. But apparently the end-user did not see that. so I guess it was OK on their machines...)
Comments are owned by the poster. All other content is copyright 1998-2025 by Bill Spitzak and others. This project is hosted by The FLTK Team. Please report site problems to 'erco@seriss.com'.
