Re: [AD] x color conversion again (w/ responsiveness patch)

[Elias Pschernig <elias@xxxxxxxxxx>]

On Thu, 2004-07-15 at 01:11 -0700, Chris wrote:
> Evert Glebbeek wrote:
> > At any rate, my problem seems to be unrelated to the recent updates so I 
> > propose to commit the responsiveness patch, either yours or Elias', 
> > whichever the two of you think is more appropriate.
> 
> They're both pretty much the same, except whereas Elias's globalizes 
> _xwin_private_handle_input, and checks _xwin_input_handler in the 
> XUNLOCK define, mine leaves _xwin_private_handle_input static, but 
> creates a new function (_xwin_handle_input_nolock) that's called from 
> the UNLOCK define and has the _xwin_input_handler check.
> 
> I think mine's a cleaner solution since you shouldn't call private 
> functions from procedures unrelated to it, but in the end it doesn't 
> matter too much I suppose.
> 
> Oh, what about the color conversion patch? I haven't yet tested it to 
> see if it'd reproduce the same glitches in non-8bit source images.
> 

I'll commit the responsiveness patch eventually, just I'd have liked
some clarity on the state of the signals version in general first - it
seems to be broken (for me in CVS, for you even in 4.1.14).

-- 
Elias Pschernig