There have been 35 issues fixed from the last snapshot7. The goal of the release was to provide a more reliable and better performing application. The resources load way faster, the logging slowdown has been fixed. There have been some user experience improvements as well, including the ability to change background of embedded CEGUI to a checkerboard. This is also the first release that supports CLI options for ceed-gui.

Hello and thanks for this new release. I had never posted on the forum before, but now I feel I should give you some user feedback. I'm not sure whether I should make it a new topic or not, but I'll leave this here since it's mostly relevant to this release.I should warn you that this may look like a rant, but I is not; I fully understand it's an independent project, with a lot of work accomplished by several contributors, and I respect that.

I compiled the current stable release of CEGUI (0.7.6) from source on Windows, to use it in an already existing project. Then, when I finally managed to do so, I tried using CEED's previous version (snapshot7), only to realize I was unable to do anything since it kept throwing exceptions. That's why I decided to download the source code of the last CE Layout Editor to work with it instead and try to add some features.Then, you released this new snapshot, and at first I was really satisfied with the improvements that had been made. It felt more polished, I only encountered one exception-throwing case (I'll make sure to open a ticket later), and I told myself "that's it, I'll use this tool since it's been greatly improved". But one issue made me reconsider it: I'm still unable to display a simple image. I had the same problem with snapshot7, it had been reported by another user on the forum (here), and a ticket had been opened on the bug tracker (here), but it seems it was closed without having been actually fixed. I've tried using custom imagesets and imagesets included with CEED in my layouts, and I've tried opening included layouts that used included imagesets, but to no avail.

The issue seems to be the same as the one reported here: CEED (or CEGUI) doesn't seem to parse correctly the StaticImage's "Image" value property, and when setting the "image" field manually in CEED, I see the same result in the "code" panel.The following is the input code from CEED's DragDropDemo layout file, set for version 0.7:

No big difference between 0.7 and 1.0: the property disappears, and the image isn't displayed.

I honestly wish I'm missing something obvious, because I can't see how such a visible issue would have made it to snapshot8 without being spotted by the developers. Otherwise, it would mean a very important and basic feature can't be used in CEED, which would stop people from using CEED, or even CEGUI.I hope I'm the only one having this problem now, and I'm ready to talk about it with a developer.

Anyway, thank you for your hard work, and sorry if I'm heavily mistaken.

Hi Shlldn,feedback is always great, thanks. This thread is appropriate, no worries.

The situation regarding Image properties is not ideal, I know. I will try to describe the reasons.

CEED only knows about images that are loaded in one of the schemes that are part of your project. CEGUI internally stores Images as pointers to the Image instances, therefore CEED can't store any Image it doesn't know about. When CEGUI loads back code you provide (or even parses a property that you edit), it tries to figure out the pointer, if such Image is not found, it sets the pointer to 0, writes it to the log and outputs an error log message.

The whole thing would be way way better if CEED had an image property editor that would only allow you to put a valid image name there.

tl;dr: Make sure you are loading the appropriate imageset in your scheme, make sure you are typing the image name exactly. Check logs (Help->CEGUI debug info).

HTH, I will target image property inspector to snapshot9 so that this gets done for the next release.

I figured I would post a reply since you were really helpful both here and on irc yesterday, and to provide some feedback about the story's "conclusion".It turns out that the .scheme file was indeed the root of the problem, since the imageset containing the images wasn't included in any of the schemes in the project. What is still troubling me is that I faced this issue after opening a project file that was included in CEED's samples directory. I expected the sample to work without any change needed, but maybe I was mistaken again.

What happened next is I added the "DriveIcons" imageset to the WindowsLook scheme (I don't think it's a good way to edit a "standard" sheme, but I just wanted to see if that would do the trick) through CEED, but then I faced another issue: my file had been emptied by CEED after saving and closing it. As discussed on irc, I filed a bug report on CEGUI's Mantis bugtracker, and kulik told me that CEED's simple text editor wasn't tested, and shouldn't really be used to edit anything. So, be extra careful with your files, and for now avoid using CEED to edit your scheme and looknfeel files, for example. I want to be clear on this: the issue only arises in "simple" text editing mode, I'm not talking about the "code" tab when editing something like a .layout file, don't avoid using CEED for that issue alone.

I then restored the empty file, made my changes with notepad, and sure enough, after reloading the resources in CEED, the pictures appeared.

I hope I made myself clear in this post.

Thanks again for your help kulik, I think I have every info I need to work with CEGUI/CEED now.

Kudos on this release. I was stuck at snapshot-5 for a long time, due to show-stoppers in later releases. This latest release is working great so far for my layout editing needs. You have really addressed a lot of the annoying usability issues and crashed, I can work reasonably efficiently within the tool now. Thnx!

The option: "prevent manipulator overlap" in Edit/Preferences/Layout editing dramatically slows down layout editing. In my case, for a layout containing ~50 widgets, the performance drops from 70fps to 0.05fps, turning this option makes it run fast again

"Prevent manipulator overlap" works in a very sub-optimal way. It uses stencil volumes to "stencil out" the parts that are overlapped by something else. Very CPU intensive. Finding the rects to stencil out is expensive as well. It could be improved to work fast but it's not a priority ATM.