You seem to be misunderstanding many of my points. (Maybe that is because I am unclear.) > A client can already arbitrarily get and set the cursor image for a

You seem to be misunderstanding many of my points. (Maybe that is because I am unclear.) > A client can already arbitrarily get and set the cursor image for a given cursor name... That is not what I am suggesting at all. My suggestion is: The client only specifies a monochrome cursor, possibly from a font; the server MAY substitute a (possibly animated) RGBA32 (or other colour type) image (for a font-based cursor) IF the user has enabled that feature in the server configuration file. > Not sure why this requires a whole new protocol version... Indeed, that is independent of the protocol. I just think it is more useful, is all.