Le 16/01/2009 21:21, Jesse Barnes a écrit : > On Monday, January 5, 2009 12:55 pm Tiago Vignatti wrote: >> Right now a thing that is annoying me is how others cursors, sw rendered, >> could be implemented. I want to avoid two differents sets of the same code >> in different contexts. IMHO conceptually all these cursor update things >> must be in-kernel. Painting a cursor image seems to be quite hard as we >> have to save/restore areas under the cursor. I remember that anholt had an >> idea concerning this, but I do not remember details. > > I really like the idea of having this in the kernel for latency reasons, but > yeah we do need to solve the sw case as well as implementing some > acceleration code. OTOH it might be reasonable to push the problem of > multiple, large, and or funky format cursors out to userspace, since those > are relatively uncommon (64x64 32 bit ARGB ought to be enough for everybody > right? :).
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. Cheers Rémi ------------------------------------------------------------------------------ This SF.net email is sponsored by: SourcForge Community SourceForge wants to tell your story. http://p.sf.net/sfu/sf-spreadtheword -- _______________________________________________ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
