FLTK logo

Re: [fltk.coredev] Towards a Wayland platform for the FLTK library ?

FLTK matrix user chat room
(using Element browser app)   FLTK gitter user chat room   GitHub FLTK Project   FLTK News RSS Feed  
  FLTK Apps      FLTK Library      Forums      Links     Login 
 All Forums  |  Back to fltk.coredev  ]
 
Previous Message ]New Message | Reply ]Next Message ]

Re: Towards a Wayland platform for the FLTK library ? Albrecht Schlosser Jun 08, 2021  
 
On 6/8/21 8:52 AM Manolo wrote:

Le lundi 7 juin 2021 à 21:03:45 UTC+2, Albrecht Schlosser a écrit :

test/doublebuffer runs "faster than ever seen" and there's no noticeable difference between single and double buffer which is what I expected. Manolo, there is no difference, right?
Yes. There's no such thing as a Wayland single window because it's not possible with Wayland to draw in the window. All drawing goes to a buffer, and then this buffer is "committed" to Wayland. The two windows of test/doublebuffer follow exactly the same code.

Thanks, that's exactly what I had expected. Wayland is always "double buffered" and, from a user's point of view, Fl_Window will be functional identical to Fl_Double_Window on the Wayland platform.

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.
Bill's hint below about the z buffer is probably the way to look to fix that. Help needed. I dont know GL.

Neither do I, but my further test (see another message) seems to indicate that the wrong behavior is Wayland and not VM specific. Do you see this misbehavior too?

Not all cursors appear as they should (test/cursor).
Yes, that happens with some Ubuntu themes but not all, and not with Debian, where all cursor shapes work.
Cursors are searched in a system folder and some shapes are absent for some Ubuntu themes. Who knows why?

Hmm, that's a pity. I don't know but I'm sure we can find a way to make our own cursors as a fallback if necessary.


Screen scaling (ctrl/+/-/0) doesn't seem to work yet. Maybe in GL windows though (not sure). I've seen some weird effects.

FTR, see attached image running "$ FLTK_SCALING_FACTOR=1.3 test/fullscreen" with both X11 (left side) and wayland (right image).

Wayland was born when HighDPI existed, so it contains natively a way to handle HighDPI in the form of an integer scale whose value
grows with pixel density.  FLTK apps follow this scaling without need for change nor ctrl/+/.

FLTK apps don't seem to honor the environment variable FLTK_SCALING_FACTOR completely (see image). The scaling factor is recognized though (scale: 1.30) in both cases.

Go to Settings -> Display -> Scale and set it to 200% or 300 % on a large display, you'll see FLTK Wayland apps follow the change.

I can't find such a setting in my Ubuntu VM. I only have "Resolution" and "Fractional Scaling" (see screenshot).

They're not adaptive while running yet, though.

Do you think you can implement this too? ctrl/+/-/0 is IMHO an essential feature independent of the system/display setting.

Manolo, would you like me to add CMake support? I'd like to help if I can.
Yes I do. Many thanks.

But I believe we should first decide whether we want to include Wayland in the FLTK repo
and whether we do that as a new branch, or in the main branch, just like Android or Pico.

I will give it a try anyway. For me it's a valuable addition even for the testing phase, and I'm confident that we will add Wayland support sooner or later -- unless we find that it's not going to work which doesn't seem likely now, thanks to your awesome work so far.

I think, as long as you're developing the Wayland port it's okay to have it in your own fork. You could even create a PR so we (devs only) can also commit directly to your fork (if you like).

My suggestion is to rebase the branch from time to time so we are always in sync with the upstream master branch (please don't merge the master into your wayland branch though, this will only make things more difficult). I do also propose that we'll rebase and squash the wayland branch before the final merge to avoid having too many intermediate file versions in the main FLTK repository.

I would also appreciate feedback about use on a native Linux system (as opposed to a virtual machine).

I'll try to test on my bare metal Linux when time permits. I think I did already install 'weston' so I could maybe run it directly on my notebook. If that's not possible I can use another Debian Buster system on my ancient MacMini. ;-)

--
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/03f181e3-2313-88cd-7472-4404c7e6fc3d%40online.de.

Attachment: fullscreen.png
Description: PNG image

Attachment: display-settings.png
Description: PNG image

Direct Link to Message ]
 
     
Previous Message ]New Message | Reply ]Next Message ]
 
 

Comments are owned by the poster. All other content is copyright 1998-2024 by Bill Spitzak and others. This project is hosted by The FLTK Team. Please report site problems to 'erco@seriss.com'.