I just found what appears to be a bug in the overlay system. It seems that when I have an overlay with one container in it, any TextArea elements inside of that container will not show. I have to add another container before it in the same overlay, containing another TextArea using the same font, so that the original one will show text. It sounds very strange, but I've tested it with a bunch of different fonts, materials, using templates / not using templates, etc. I am using the latest MogreSDK (which uses OGRE 1.7.1 revision 72), so I'm not sure if it's a Mogre-specific problem. Could someone else confirm / disconfirm this? Thanks!

i replied for this problem earlier another thread..I think this is bug in OverlayElement::_update(void) function,mPixelWidth is changed at line (1) , but mWidth is changed at line (2)but at line (3) mGeomPositionsOutOfDate is setting to false, so when next _update fuction called, line (2) is not excuted because (4) is falsemWidth is not changed at this time, so textarea is not displayed

// load fonts explicitly after resources are loaded (esp. SdkTray.zip) since they will not be loaded on start up from the resource manager ResourceManager::ResourceMapIterator iter = Ogre::FontManager::getSingleton().getResourceIterator(); while (iter.hasMoreElements()) { iter.getNext()->load(); }

Fonts are not loaded correctly in the first run... So add these lines at startup after you loaded your resources (esp. SdkTray.zip)!I had this problem with sliders, labels, buttons and so forth.

guillaumequest wrote:Hello, I believe I'm still having this bug, but I'm not using SdkTrays, just overlays directly, and all the fixes use SdkTrays. Do you know if there are some other fixes available ?

Thanks for your help, Guillaume

If you're compiling Ogre, you can look up a few posts for a solution that involves changing OgreOverlayElement.cpp.Also, from the other threads: "Any operation that will cause the OverlayElement's geom positions to be refreshed will fix this problem."This includes stuff like changing positions and sizes, and setting the metrics mode.

Thanks, I copied the code from ObjectTextDisplay and adapted it so that it would display the text at a fixed position and this worked for some reason, I don't really have any idea why that worked better, though...

It seems the patch has broken the ability to update the position of an overlay element with setPosition(...) when element is in relative mode. It seems the switch case in _update() should be similar to the one in _notifyViewport(), i.e. add to the default case: