[PATCH weston 08/13] Remove support for text cursor position based output zooming
spitzak at gmail.com
Sun Oct 13 22:38:21 CEST 2013
Sorry, misunderstood your patch. You are not removing the text cursor
position, just the ability of the demo shell to zoom in on it.
On 10/13/2013 01:35 PM, Bill Spitzak wrote:
> On 10/12/2013 08:38 PM, Jason Ekstrand wrote:
>> The entire concept of a text cursor position requires a concept of a
>> "primary view". While this could be implemented in a shell, the current
>> implementation crosses the shell/compositor line in strange ways. For
>> it is simplest to just remove support for this. If we decide we want it
>> in the future we can reimplement it then in a more sane way.
> Ah this shows why you are concerned about the "primary view".
> Popups created by the input method should behave *exactly* the same as
> popups created by the client. So removing this stuff is not going to
> solve anything (unless you also removed the ability for clients to make
> popup windows, which I don't think you did).
> It would be nice if popups only appeared on one view, so a "primary
> view" may be a good concept to add in the future, and it effects both
> input methods and client-requested popups. Probably should be optional
> and left to the compositor to decide, so that compositors can implement
> cloning by sharing the same composited buffer. The method of determining
> the "primary view" can be compositor-specific, since whether or not
> there is one is compositor-specific. (I would try a view that is on the
> same output as the mouse cursor, but I bet some people here will hate
More information about the wayland-devel