<html> <head> <base href="https://bugzilla.gnome.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - Wrong (ultra tiny/small) cursor size on HiDPI screen" href="https://bugzilla.gnome.org/show_bug.cgi?id=744932#c40">Comment # 40</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - Wrong (ultra tiny/small) cursor size on HiDPI screen" href="https://bugzilla.gnome.org/show_bug.cgi?id=744932">bug 744932</a> from <a href="page.cgi?id=describeuser.html&login=jstpierre%40mecheye.net" title="Jasper St. Pierre <jstpierre@mecheye.net>"> Jasper St. Pierre</a> <pre>I consider nested X11 a developer tool only, so we haven't given it the real attention and split it out to a "true" backend. Things like barriers and input settings really shouldn't be running as nested X11 either. Note that I already have an enum here for what you call "running mode" to cut down on the "meta_is_wayland_compositor" in the backend code. <a href="https://git.gnome.org/browse/mutter/tree/src/backends/x11/meta-backend-x11.c#n49">https://git.gnome.org/browse/mutter/tree/src/backends/x11/meta-backend-x11.c#n49</a> But personally, I don't care enough about the nested code -- it's not production, it's development and testing only, and as long as it's not too messy, let's not overcomplicate things. I'm fine with having nested not use a X11 cursor and instead always draw it ourselves, for instance. It's why we call XFixesHideCursor even in nested mode. If you don't like that you don't have a cursor sometimes, move your mouse back over the nested window enough that it shows again, and then alt-tab to another window. If you feel really encouraged to fix this, feel free, but I've just not bothered.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are on the CC list for the bug.</li> </ul> </body> </html>