Hi, Last time I write about this: indeed, dano and haiku use all 255, for the colorkey and masks, so the driver gets correct info. (unfortunately haiku still becomes unstable and slow if I enable logging in my drivers: they log a lot.) I guess my last conclusion was correct then: overlay window shows incorrect color. Sorry for bothering this long :-/ Rudolf. > Hi Axel, > > I guess I'm a bit dumb. And I'm now drinking a beer, which probably > doesn't help either :) > > So, you're saying that the app is not displaying the correct color > onscreen? Sorry, I still don't get it... I think the problem is that > you and Stephan look from the app_server perspective with all > knowledge > of it's inner workings, while I am looking from the opposite > direction: > the drivers. I just see a black box not behaving as it should, I just > know about the interfaces to the app and the driver, that's why I am > trying to get a full sentence out of you guys just plain and simple > telling me where the problem lies (English for dummies so to speak). > > So: do you think I ask stupid questions, wasting your time? Just let > me > know and I'll shut up, and forget about testing Haiku again (for > now): > concentrating on the established versions of BeOS to just continue my > 'core business'. ;-) > > Bye! > > Rudolf. > > > > > > > "Rudolf" <drivers.be-hold@xxxxxxxxxxxx> wrote: > > > And how about the color(index) drawn in the output window that > > > displays > > > overlay? Index 255? > > > It doesn't work here, you know... (last time I checked, and I > > > didn't > > > see commits that suggest it was modified since?) > > > > Exactly, that's where the problem is right now; we don't have a > > method > > to specify an index when drawing on screen yet, IOW eeet's br0ken : > > -) > > > > Bye, > > Axel. > > > > > > > > >