Re: Wayland and Gambas

[Bruce Steers <bsteers4@xxxxxxxxx>]

On Sun, 7 Apr 2024 at 21:27, Benoît Minisini <
benoit.minisini@xxxxxxxxxxxxxxxx> wrote:

> Le 07/04/2024 à 22:10, Bruce Steers a écrit :
> > With the greatest respect to Ben i have to say,, I'm not so convinced it
> > is just a wayland is broken thing I think gambas is missing a trick.
> > I mean, I can load gnome files or gnome text editor and they open at the
> > last opened position not just 0,0 .
> > they seem to know and remembrer their screen position jut fine.
> >
> > So I think it's a gambas problem/misconception as it seems like only my
> > gambas apps that have zero control over window positioning on the screen.
> > Respects
> > BruceS
> >
>
> If I run "meld" on KDE, which is a GTK+ application, it opens at a
> random position. It does not remember its last position.
>
> As there is no Wayland protocol to specify a window position, KDE and
> Gnome have to implement their own private protocol to let an application
> move its windows, and/or automatically remember the position of the
> windows of the applications.
>
> But then it will work only for gnome applications on a gnome desktop,
> and KDE applications on a KDE desktop, as long as these private
> protocols do not become a common Wayland standard protocol.
>
> --
> Benoît Minisini.

Seems crazy.  surely it means lots of things are broken for us?
Even with gambas.

Mouse.ScreenX and ScreenY for example. A quick search for Mouse.ScreenX in
the gambas sources and i find this...

Gambas3 IDE : 36 matches
gb.form : 18 matches
gb.gui.base : 5 matches

i see it used in many places , gb.form.editor , gb.form.terminal
Does all that code function correctly knowing in wayland we actually get
Mouse.X not Mouse.ScreenX?

I just had to reset my Suse VM using wayland just because i loaded the
DBusExplorer and used the scrollbar.  after letting the scrollbar go it
just carried on moving very slowly and i lost all mouse control, the
scrollbar finally stopped at the bottom of the list but the VM was totally
locked up.
It could have been anything but i can't help thinking it's probably a
gambas bug.
Gambas and wayland just seems like pretty dangerous ground.

Maybe gambas could implement a way (private protocol) to work around these
problems too?

Respects
BruceS