X always must have a cursor

Kiryl Hakhovich khakhovich at bsolution.net
Wed Jul 15 04:53:27 PDT 2009


On 07/14/2009 10:29 PM, Peter Hutterer wrote:
> On Tue, Jul 14, 2009 at 07:21:29PM -0700, Sean Estabrooks wrote:
>    
>> On Wed, 15 Jul 2009 12:12:50 +1000
>> Peter Hutterer<peter.hutterer at who-t.net>  wrote:
>>
>>      
>>> the concept of having one pointer is built-in into the X protocol. so while you
>>> could remove the pointer from the server, applications will fail in quite
>>> interesting ways because they don't expect it. believe me, I've tried.
>>>        
>> I think that is Kiryl's answer right there.  At a low level you just can't
>> "turn off" the concept of a pointer.
>>
>>      
>>> however, nothing in X requires you to _use_ a pointing device.
>>> I realize that some applications UI do not provide sufficient alternatives
>>> for keyboard navigation. That's not the X server's fault though.
>>>        
>> Which makes one wonder why the low level protocol makes such demands.
>>      
>
> it was designed in the 1980s, and up to now the concept of a pair of input
> devices, once location based, one focus based is still quite widespread.
> I really don't know what your use-case is that requires the concept of the
> pointer to disappear.
>
>    
>>> wouldn't the simple solution then be to deactivate the touchscreen?
>>>        
>> It sounds as if there is no alternative.
>>      
>
> well, if you have an input device and you don't want it to do anything, you
> need to deactivate it. if you have a keyboard and you don't want it to do
> anything, it's easier to deactivate the keyboard rather than remove the
> concept of a keyboard from the GUI.
>
> Cheers,
>    Peter
>    


i guess all that make sense somewhat now. thanks guys.

kiryl
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.x.org/archives/xorg/attachments/20090715/e4c54ced/attachment.html>


More information about the xorg mailing list