[PATCH weston] window: allow changing cursor theme and size

Pekka Paalanen ppaalanen at gmail.com
Wed May 16 02:17:29 PDT 2012

On Wed, 16 May 2012 10:03:55 +0100
Daniel Stone <daniel at fooishbar.org> wrote:

> Hi,
> On 16 May 2012 08:21, Pekka Paalanen <ppaalanen at gmail.com> wrote:
> > On Tue, 15 May 2012 11:09:36 -0400
> > Kristian Høgsberg <hoegsberg at gmail.com> wrote:
> >> Right, we only parse that in the desktop-shell client.  I don't know
> >> then, maybe we should go back to shipping a cursor theme with weston
> >> that we can fall back on if loading fails.
> >
> > That would feel like a step back in cleanups.
> >
> > When an X11-independent part is split out from libXcursor, maybe it
> > could grow an API for saying "look for <insert-name-here> theme

Oops, insert-name-here should denote Wayland, X, whatever environment.
Just in case someone thought it was a theme name, no.

> > configs", and the X11 part would hardcode the current behaviour.
> In that case, would it not just be easier to move the part that checks
> the XCURSOR_{THEME,SIZE} environment variables out of X11-specific
> code?

Sure, but then you'd have XCURSOR_* env vars with something that is not
called libXcursor, has nothing to do with X, and could still mess up
with X.

I think it would be nice if it automatically tried to open
$HOME/.config/wayland/cursors/index.theme or such. Would not need to
set up env vars at all.

Just thinking out loud,

ps. Telling me to just use the same cursor theme for both X and Wayland
is fine, too, if you think this is getting too far. And I suspect that
is what most people would want.

More information about the wayland-devel mailing list