On Sun, Mar 23, 2003 at 09:52:33PM -0500, [EMAIL PROTECTED] wrote: > I was using EXCLUSIVE and found it was not working but did start > working after I changed it to ADMINISTRATIVE. > > Is there an explanation of what these co-operative levels are and what > they do?
I'm not sure if they are mentioned in the API docs since I've never really read them. Instead I just read idirectfbdisplaylayer.c ;) > Now I just have to go hack the SetOpacity calls in MPlayer's vo_dfbmga > again so that my screen is not black when returning from mplayer back > to my gtk gui. Was there any agreement on what is the best way to > handle this sitution rather than MPlayer arbitrarily setting the > opacity on exit? The real solution is reference counting. Still only FIXMEs. > Is this something that I can have my "mplayer > launcher" correct when it resumes control after mplayer's exit? You could call SetOpacity from the launhcer. The screen will blink but then again it would blink anyway when the pixelformat is changed back to RGB32. Not sure if that's any better than patching mplayer though. -- Ville Syrj�l� [EMAIL PROTECTED] http://www.sci.fi/~syrjala/ -- Info: To unsubscribe send a mail to [EMAIL PROTECTED] with "unsubscribe directfb-dev" as subject.
