[PATCH 0/4] Cursor's update inside kernel only

McDonald, Michael-p7438c Michael.McDonald at gdc4s.com
Mon Jan 19 10:46:43 PST 2009


 

> -----Original Message-----
> From: xorg-bounces at lists.freedesktop.org 
> [mailto:xorg-bounces at lists.freedesktop.org] On Behalf Of Jesse Barnes
> Sent: Monday, January 19, 2009 11:03 AM
> To: dri-devel at lists.sourceforge.net
> Cc: xorg at lists.freedesktop.org
> Subject: Re: [PATCH 0/4] Cursor's update inside kernel only
> 
> On Friday, January 16, 2009 1:55 pm Rémi Cardona wrote:

> > Not for firefox. Any drag&drop in gecko will result in huge ARGB
> > cursors. Even just dragging and dropping a tab results in a cursor
> > that's at least 150x20px.
> 
> Gah, yeah forgot about drag & drop of big icons...  Maybe 
> Kristian was right 
> that all cursors should be done in software; hardware just 
> doesn't provide 
> the flexibility desktops want these days.

  Are they (Firefox/Gecko's d&d) really X cursors or are they pixmaps tracking the cursor? If I'm moving a window, is it OK to define the cursor to be a fullsize image of that window? 

  I'd so no, cursors are small, limited icons. In "X Window System" by Scheiler & Gettys, it says "The components of the cursor can be transformed arbitrari;y to meet display limitations" (pg 178) and "Applications should be prepared to use smaller cursors on displays that cannot support large ones" (pg 180).

Mike McDonald
GDC4S/FCS/PVM/SDC 



More information about the xorg mailing list