On Sun, 2008-12-21 at 19:12 +0100, Dirk Meyer wrote: > Dirk Meyer wrote: > > I want to disable slicing for some textures to make the reflection > > texture from tidy work. Since I have an Intel card, I have sliced > > textures and from what I found out, I need to disable slicing for the > > reflection: > > > > | WARNING **: cogl_texture_polygon does not work for sliced textures when > > the minification and magnification filters are not CGL_NEAREST > > > > So how do I do that? It is a property for Texture, but it must be set in > > the constructor. How do I pass disable-slicing to Texture()? > > Using pyclutter-0.8.2. The question is how to pass properties to a > Python constructor.
unless there is a way to call g_object_new() from pygobject-based bindings, then no: there is no way to set this property. I could prolly add every construct-only property in Clutter to the relative constructor in pyclutter, but looking at :disable-slice I'm a little bit puzzled about it. the CoglHandle used by the texture is created inside the load_from_* methods instead of being lazily created inside the ::realized handler. I guess this is done because of FBOs and Clone textures, but I don't understand why clutter_texture_new_from_actor() or ClutterCloneTexture cannot also call clutter_actor_realize() on their sorce. if that would be possible then we could simply make :disable-slice unrealize the texture actor (if at all needed). or maybe I'm simply on crack - I admit the Texture code feels like it's composed of heuristics that have been collected on the various GL implementations to shield the developer from actually care about all this mess. :-) in any case, fixing pyclutter is not a big deal. ciao, Emmanuele. -- Emmanuele Bassi, Intel Open Source Technology Center -- To unsubscribe send a mail to [email protected]
