dead space elimination

Jozef Riha jose1711 at
Mon Sep 28 02:52:21 PDT 2009

On Thu, Sep 17, 2009 at 3:53 AM, Dave Airlie <airlied at> wrote:
> On Thu, Sep 17, 2009 at 2:18 AM, Vincent Legoll
> <vincent.legoll at> wrote:
>> On Wed, Sep 16, 2009 at 4:20 PM, Rémi Cardona <remi at> wrote:
>>>> I'm even thinking of different warping policies:
>>>> - translate: warp to suitable location on other screen
>>>> - blocking: stay on the current screen, do not enter forbidden area
>>>> - jump into corner of the other screen
>>>> but maybe only one of those will feel "natural"
>>> You guys might want to look into what's been done by HCI researchers in this
>>> area.
>>> One such article that comes to mind is "Mouse Ether" [1] which describes and
>>> tries to address the problems of dead space between monitors.
>>> There are many more articles on the topic in various HCI related
>>> conferences, those might definitely be a good start as those folks have
>>> already cleared a lot of theoretical and technical problems.
>> Very interesting indeed, but far too early to get into such
>> details.
>> What I had in mind when I wanted detailed instructions
>> about how to do it would be of the kind:
>> "Look at method PointerMove() from file /path/dir/mouse.c"
>> or something like that...
> hw/xfree86/modes/xf86Cursors.c
> xf86_crtc_set_cursor_position + xf86_set_cursor_position
> along with whatever ends up calling them.
> hw/xfree86/common/xf86Cursors.c
> Dave.

this also looks interesting
though (heavily?) dependant on latest KDE


More information about the xorg mailing list