some questions about v0.9.6b

huaner

08-09-2007 12:51:22

hi:
i just download the v0.9.6b. Is the FreeType2.3.5 downloaded by myself?
and it will creat more than six windows by v0.9.6b?
thank you very much!

kungfoomasta

08-09-2007 18:08:01

It doesn't need FreeType library, it uses Ogre's Font class, which uses FreeType, which is bundled in Ogre's dependencies.

I haven't tested this, but there is no limit on the number of windows. Now that I control all rendering and creation of widgets without using overlay containers etc. I don't see any problems with creating a lot of windows. If you do run into a problem, I will be much more able to help fix it.

huaner

09-09-2007 02:58:40

It doesn't need FreeType library, it uses Ogre's Font class, which uses FreeType, which is bundled in Ogre's dependencies.

I haven't tested this, but there is no limit on the number of windows. Now that I control all rendering and creation of widgets without using overlay containers etc. I don't see any problems with creating a lot of windows. If you do run into a problem, I will be much more able to help fix it.

hi.
but when i run the demo, there is a exception: the texturn is not large enough to fit all widget images in QuickGUIImageset. the resources are include the v0.9.6's zip.

kungfoomasta

09-09-2007 07:18:02

You have to update the images used. I lowered the size of the qgui.image.png file. To avoid problems, just wipe QuickGUI completely, and work only with the release package I have provided.

huaner

09-09-2007 08:10:13

You have to update the images used. I lowered the size of the qgui.image.png file. To avoid problems, just wipe QuickGUI completely, and work only with the release package I have provided.
oh, i make a mistake when copying resources. but when i run the exe, the createScene is all right. but when createFrameListener, there is a run_time check failure #0 when go to windowResized(). why?

kungfoomasta

09-09-2007 08:49:01

heh, you ask that question as if you expect me to have had problems running the demo on v0.9.6. :lol: I have no idea why you get a run_time check failure. What is the callstack?

huaner

10-09-2007 02:33:35


The not recoverable stack pointer problem is usually, as the message suggests, a calling convention problem. You call a method with one convention (say register saved arguments) but the called method tries to pop them from the stack.
This can happen when you the lib you linked against doesn't match the DLL you are trying to run it with, so maybe you tried to run with an old OgreMain.dll or so?

i search this in the ogre forum. i use Ogre 1.4.0. maybe is the match question?

kungfoomasta

10-09-2007 04:19:44

From that description is sounds like you are using an old version of QuickGUI.dll, or QuickGUI_d.dll, with the new version of the library. You should delete all your QuickGUI .dll and .lib files, rebuild them all, and try to run the demo again. :)

huaner

10-09-2007 08:06:27

i just download ogre v1.4.3 and try it. it's all right. i think i used an old version OgreMain_d.dll.
but when i compile the QuickGUIEditor

error C2661: 'QuickGUI::GUIManager::GUIManager' : no overloaded function takes 2 arguments

so, i change
mGUIManager = new QuickGUI::GUIManager(this->Width,this->Height);

to
mGUIManager = QuickGUI::GUIManager::getSingletonPtr();
mGUIManager->setup(this->Width,this->Height);

but, the .exe can't run. it has a runtime error. and if it can run successfully, how to use it? and how to bind it to gui solution?
the last quesiton is:
i wrap a class that load a .xml file,and then creatGUI what i need. but i found the api of creating widgets is different between v0.9.6b and v.0.9.4. so, i have to rectify the our api. i feel it's very troublesome. :( i just propose a suggestion. but, i thank you all the same. :D

kungfoomasta

10-09-2007 16:09:49

The editor doesn't work right now, because the API changes a lot with every release, and I decided not to work on it for the time being. We're trying to keep design changes to a minimum, but some changes are needed, to keep the library clean and easy to maintain and add to.

I have plans to tackle serialization, but not until 2 more releases or so. v0.9.7 will have a lot of changes in the library, so I wouldn't put effort into the xml layouts just yet.