CEGUI (Crazy Eddie's GUI) Forums

EDIT: This has been fixed by cfab39dac3b7. See page 3 for workarounds on prior versions.

Original message below:
_____________________________________

Hello,

I just ported my application from Ogre 1.8 and CEGUI 0.7 to Ogre 1.9 and CEGUI 0.8.4


One difference that I have noticed is that all the ItemListbox widgets in my application have stopped rendering their last item entry.

I have written a sample that reproduces this behavior.
Here's the extract regarding the ItemListbox widget:

On my machine, this code shows a single listbox with only two items ("item #1" and "item #2") instead of the expected three.
Enabling the last two commented lines solves the problem, but doesn't seem very mmm... clean since onRootWindowChanged is protected.

There must be some piece of code triggered by the call to onRootWindowChanged that forces a full redraw/refresh of the view. What is that piece of code? How can I call it outside of onRootWindowChanged?
Invalidate doesn't either work as I'd expect in this case...

Here's the full sample that reproduces it on my machine (a Gentoo linux box, Ogre and CEGUI compiled by portage) :

You shouldn't have the ItemList as the app's root window. I'd recommend to first set some DefaultWindow as root window and then add the ItemList to this DefaultWindow.
The DefaultWindow should have relative sizes of width 100% and height 100% to completely fill the app's window.

Thank you lucebac, but it seems you didn't understand my issue.
In my application, I do precisely as you recomend. The code copied in my first post is the most simple sample that reproduces the issue on my machine.

EDIT:

1. I added a DefaultWindow as the root window and as a parent for the listbox. If the listbox is linked to the default window before items are added to the listbox, I observe the same issue as before.
2. However, if the listbox is linked to the default window after items are added to the listbox, I observe all expected items in the list box.
3. I'll edit the original post to make the question more clear.

From there I can clearly say that you make the ItemListBox the root window. Please try the following:


Anyways, where is your CEGUI log?

lucebac wrote:From there I can clearly say that you make the ItemListBox the root window. Please try the following:

Already did. Please see the EDIT in my previous post.

Anyways, where is your CEGUI log?

Here it is. I didn't see anything interesting in it.

Hm. Have you tried running the WidgetDemo and checked whether your bug occurs there as well?

lucebac wrote:Hm. Have you tried running the WidgetDemo and checked whether your bug occurs there as well?

No. I'll be away from my machine for the next few days. Anyway, whether this bug happens with another sample code will mostly depend on the order of operations that code uses (see previous posts).
The most interesting information for now is whether my bug affects other setups too, or only my machine.
In the former case, this means this is a CEGUI or Ogre bug (and I tend to lean that way as this looks like a case of sequential coupling, for now).
In the latter case, this means this is either a video card (software or hardware) issue or that something is wrong with the binaries built on my machine.

What happens if you choose CEGUI's OpenGL Renderer, instead of the Ogre Renderer, with the same code?

Hello Ident.
Thank you for the reply. I had thought to try what you propose, but didn't have enough time then. I'll try ASAP and post the results.

Okay good, just report back asap and we will try to help asap.

The reason why I asked you about the other Renderer is so that we can narrow down the issue. I want to find out if this is purely a rendering issue or one in CEGUI Core (unlikely).

Yes, we understood each other.
I just spent a couple hours trying to get CEGUI's OpenGL renderer to work with either SDL or by talking directly to glut, to no avail.
I've never used CEGUI with anything other than Ogre. If I send you SDL/glut code, would you have time to review it?
(I leeched most of the SDL code from here.)

No, unfortunately I dont have time for this. If you have a properly coded and working solution make a PR. However, there is currently a PR for SDL2 pending. Do you use SDL1 or SDL2? If you use SDL2 there are solutions out there already.

Edit: Mandatory link - https://bitbucket.org/cegui/cegui/pull- ... e-and-sdl2
This has not been merged but we are soon merging it.

I've been using Gentoo's libsdl-1.2.15 package.
I'm done for today. I'd rather not move to SDL 2 or replace my distro's package with git code for now.
I'll see when I have more time.

Just to clarify, whether you use SDL1, SDL2, freeglut, openglut, glfw, whatever else, it does simply not matter. The only difference is how you handle input, create your window, notify CEGUi of changes etc.

What matters is that there is an OpenGL context and CEGUI only depends on OpenGL. The PR changes I asked for would be for the application templates and sample browser. Nothing in CEGUI needs to be changed in order for it to work in SDL1 and it has been used with SDL1 many times. If you didn't change any OpenGL states then CEGUI should just render correctly.

Well, now I am lost.

Compiling the SDL code previously linked, only changing stuff related to resource loading, gives me a black window where the GUI takes only one ninth of the window (one third in height, on third in width) with the mouse cursor inverted on both X and Y axes.

Since the GUI is so small, when adding my item listbox code, I can't figure out how many items are rendered in the list.