Maybe something like this would work:
'Is there a depth close to my own depth, take that'
if not, take the depth nearest, but lower than my (where my is display)
depth.
But I agree, the current 'depth' system is just suck.
I want to a plugin to be able to say "I support these depths",
"pick one that you'd like", but as well "I will now start with
outputing THIS DEPTH", (for example for the gdkpixbuf plugin,
you don't know what depth the image has, so the plugin has to
be able to notify in realtime)... I'm undecided howto do this
right, but now we're doing libvisual-display, this might be the
right time to fix this... I must admit tho, that I'm really kinda
undecided. There are a few steps in this:
1. Plugin requests depth.
2. If plugins ran within a VisActor the VisActor has to catch
this notify, and resynchronise with the plugin. (and
possibly revise the depth transformation environment).
3. The app needs to be notified, Maybe the app runs it in this
depth itself. And then resync with the VisActor..
So actually, the app needs to know BEFORE the VisActor knows, but when
it gets a request, it should handle it by resyncing the VisActor.
Now we get at the point we need an event loop within the APP.
This makes it harder to use libvisual, which kinda suck...
I'm not sure, please think with me :)
Cheers,
Dennis
On Mon, 2004-10-04 at 23:46 +0300, Vitaly V. Bursov wrote:
> Some actor plugins support multiple depths...
> How it should be choosed? It's a difficult to choose
> the best depth - it's too plugin specific.
>
> I propose to add a function to actor plugin API which
> gets available depths as its argument and returns only
> one depth that plugin performs best. Anyway there must
> be manual override.
>
> Not sure. Suggestions?
>
|
