<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#c33">Comment # 33</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=jadahl%40gmail.com" title="Jonas Ådahl <jadahl@gmail.com>"> Jonas Ådahl</a> <pre>(In reply to Owen Taylor from <a href="show_bug.cgi?id=744932#c28">comment #28</a>) > So this is a pretty big patch set - so I wanted to stop back and discuss > where we want to go with this for 3.16. > > * Is there some simpler patch that just fixes the initial bug report and > gets us to the point where we aren't regressing from X and using the wrong > cursor size when there's only one monitor? It looks like GTK+ tries to > create a cursor of the right size. What if we just used the cursor set by > the application pixel-for-pixel ignoring the scale set on it? (Or are we > already doing that and the problem is the lack of proper enter/leave events?) > > * If we want to land this full set of patches, what I think we should do is > wait until 3.16.1 (which is Monday, I think anyways?) and mutter is > branched, and land them on master, and then look at backporting once they've > had a little chance to get some testing and mature. I suppose we could just always load bigger version of the theme in that case. I can look into that on Monday.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are on the CC list for the bug.</li> </ul> </body> </html>