|
|
On 6/8/21 2:30 PM Albrecht Schlosser
wrote:
On 6/8/21 8:52 AM Manolo wrote:
I would also appreciate feedback about use on a native
Linux system (as opposed to a virtual machine).
My test results follow...
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.
FYI, from Wikipedia: "Weston is the reference implementation of a
Wayland compositor also developed by the Wayland project."
https://en.wikipedia.org/wiki/Wayland_(display_server_protocol)#WESTON
Since I had already installed weston (Ubuntu package: weston, maybe
together with some more '-dev' packages) I could build the FLTK
wayland branch w/o installing anything else on my Linux Mint 20
system (which is based on Ubuntu 20.04 LTS).
I launched 'weston' which opened its own desktop window. All (FLTK)
Wayland programs connect to this weston instance and show their
windows on this weston desktop. Screenshot 'weston-wayland-x11.png'
shows the weston desktop in the background, two FLTK Wayland
programs on the left hand side, and two FLTK X11 programs on the
right hand side in front, overlapping the weston window. The
glpuzzle demo under Wayland exhibits the know issues.
For devs who can't test themselves I'm attaching the screenshot
'weston-fullscreen.png' so you can get an impression.
@Manolo: I showed intentionally the cursor FL_CURSOR_SE that (IIRC)
did not show properly in my first Ubuntu test which seems to confirm
what you wrote about cursor images.
Screenshot 'lines.png' shows a zoomed image of
'test/unittests:drawing lines' with pretty anti-aliased lines.
I also found a new bug which is described in attached
'wayland-error-in-client.txt': the first part shows the info
displayed when running the program and clicking on
'fl_show_colormap()'. The program window disappears and lines 3-4
show an error message.
The "Error message in weston" is logged by the running 'weston'
instance and may be interesting as well.
After this the running 'test/color_chooser' uses 100% CPU time and
needs to be stopped with ctrl/c.
Other observations in this constellation with weston:
- mouse clicks seemed sometimes not to react immediately (maybe
flushing the display was missing), but then it worked again
flawlessly
- this also affected window resizing with the mouse (sometimes, not
always)
- test/offscreen seemed to hang after the start, but after clicking
on another window (multiple times IIRC) it seemed to work as
expected
As I wrote above, these are observations running on my bare metal
Linux Mint with weston. It is possible that the interaction with
weston caused some of these effects. More tests with a "Wayland
desktop system" like Ubuntu are needed.
--
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/59d34422-a4fe-511c-35e5-6ed8fd9a66d7%40online.de.
Attachment:
weston-wayland-x11.png
Description: PNG image
Attachment:
weston-fullscreen.png
Description: PNG image
Attachment:
lines.png
Description: PNG image
Run 'test/color_chooser'
Click 'fl_show_colormap()'
... shows the following error message (xdg_surface...):
$ test/color_chooser
makeWindow:0x7ffcce12f118 wl_compositor_create_surface=0x1f9e780 scale=1
makeWindow:0x7ffcce12e598 wl_compositor_create_surface=0x20417d0 scale=1
makeWindow: xdg_wm_base_get_xdg_surface=0x20f1ca0
xdg_surface@34: error 3: xdg_surface has never been configured
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Error message in weston:
[16:06:32.781] libwayland: error in client communication (pid 53444)
'top' shows 100% CPU activity of test/color_chooser:
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
53444 albrecht 20 0 30392 18112 14656 R 100,0 0,1 1:50.92 color_chooser
-------------------------------------------------^^^^^
[ Direct Link to Message ] | |
|
| |