Horde3D

Hi. I'm trying to create gui so i have been playing around with showOverlay(). I ended up to situation where i need to know dimensions of image being drawn. Is there any way get that information?
I tried use getResourceParami() in a few different ways, but i got out only 0.

Don't know why you have chosen ResourceType::Material as the topic, but to query the texture size you have to use
getResourceParami(TextureResParams::Width) or Height

I tried that too, but it returned 0.

Are you sure your texture is loaded? Did you check the log for errors? Did you pass the texture handle to the function(not the material handle)?

Whole problem here is that showOverlay seems to want handle for Material, not Texture. If i try feed it with Texture it will whine about it not being eglible resource type. So what i want is to get Texture out of Material, which seems to be somewhat impossible.

What about using Horde3D::findResource ?

That returns name of xml file for material.

edit:excuse me, i mistake for another function...
edit2: findResource takes filename/path for image, so if i know it, it will work fine. But where from i get that filename then?

We will very soon have improved resource data handling. This should solve your problem.

Looks promising. When is very soon?

I found temporary solution for my problem. It's dirty and i have no idea what unwanted side effects it might bring, if any.

So, practically i'm misusing material class like this:

And in code:


Dirty, but it works. Will there be any side effects/problems if i'll do this?

I can't imagine that there should be any sideeffects, since it only calls getter functions.

Not sure, what you mean with this:

The resname of the material is irrelevant for the call to findResource. There you need the texture resource name, not the one from the material.
But since your solution works, I guess it's just a typo in your post.

Oh, be damned my keyboard, making typos while i look away...

The material class is only referenced in the pipeline for limiting rendering to a specific class of objects (e.g. only tranparent objects). I don't expect side effects with the sample pipelines. But of course, as you state yourself, it is just a hack (although a clever one) and should be replaced as soon as the new material interface is ready (maybe in a few days).