alfredon996

My goal is to code basic buttons and understand how operating systems implement the way they draw windows for applications.

So do you want to program a GUI yourself, and not using a library, correct ?

For that you need a ROM that supports signature spoofing, but it should be possible, just not for the common user, sadly

I understand, but if the application opens the browser you have to make it believe that it is opening Chrome

Have you tried changing the user agent ? You need an extension for that

Thanks for the detailed answers. So we can say that Wayland sacrifices lower latency in exchange for higher accuracy.

According to this post Gnome allows you to change this behavior through an environment variable (MUTTER_DEBUG_ENABLE_ATOMIC_KMS=0 on Ubuntu 22.04). It should be a configurable option, considering the amount of people complaining about this mouse behavior.

Oh and this is also why the cursor movement might visibly start stuttering during heavy GPU load. This is a problem that was solved back in the 80s but here we are…

Sad, but does this problem only affect Wayland or also Xorg?

For example, the recently publicized about mouse latency differences is true and something I’ve noticed but the difference doesn’t particularly bother me. Something like that is just one of those inevitable consequences of the design of Wayland being so fundamentally different.

It would be interesting if someone explained the relationship between Wayland design and mouse latency