Layout Editor

[Banania]

Hi,

Thank you for your job ! The community really need this tool !

I played a bit with your new version and with the new background functionnality.

Here is some feedback:
*When I set a background to show, my gui windows are not correctly displayed. Some parts of the window don't get displayed.
I don't know if I am clear and I cannot host a screenshot anywhere right now so I hope you understand.
*When you click on an item in the tree view, sometimes, it is not the good item that gets selected. I know that one had already been adressed but it cannot harm to say it again.

Well, keep up the good work !

[PeterNewman]

Just like to add, if you could possibly bring this to the current version of CEGUI? The widget naming changes I worked so hard to put in with the updates mean I cant use this useful tool!

Perhaps if you brought it up to use the new naming convention, and used the alias file that CE has for the old names as well, this should support people at both stages.

Also, can you somehow handle layout schemes that use <GUILayout Parent="root">. Last time I tested this didn't work, and I don't know if you've gotten it working since. But because I split up my layouts into multiple files (load the ones I need at the time), I use the Parent attribute.

Other then that, looks good!

[scriptkid]

Hi,

Thank you for your job ! The community really need this tool !

I played a bit with your new version and with the new background functionnality.

Hi! Thanks for the comments and checking the new functionality!

*When I set a background to show, my gui windows are not correctly displayed. Some parts of the window don't get displayed.
I don't know if I am clear and I cannot host a screenshot anywhere right now so I hope you understand.

I think i know what you mean, i see it happen at my own system too sometimes. It seems like an invalidating problem of the view. I will give it a try to fix it.

*When you click on an item in the tree view, sometimes, it is not the good item that gets selected. I know that one had already been adressed but it cannot harm to say it again.

mmm, i missed this one, so its good you mentione it again. Again, i will look into it.

Thanks!

[scriptkid]

Just like to add, if you could possibly bring this to the current version of CEGUI? The widget naming changes I worked so hard to put in with the updates mean I cant use this useful tool!

I will try to migrate to the latest version. Shouldn't be that much troubles i think.

Perhaps if you brought it up to use the new naming convention, and used the alias file that CE has for the old names as well, this should support people at both stages.

Another thing to look into

Also, can you somehow handle layout schemes that use <GUILayout Parent="root">. Last time I tested this didn't work, and I don't know if you've gotten it working since. But because I split up my layouts into multiple files (load the ones I need at the time), I use the Parent attribute.

Ok, sounds like a real requirement. I will look into it.

Other then that, looks good!

Thanks!

[Banania]

I think i know what you mean, i see it happen at my own system too sometimes. It seems like an invalidating problem of the view. I will give it a try to fix it.

It definitely seems like it is an invalidating problem. It is pretty annoying as it appears quite often on my computer, especially when I move widgets

I remember having the same kind of problems some times ago when I was writing an editor at work. I found some nasty workarounds for that and never really tried to find a real clean solution because I had no time for it.

Good luck ...

[Banania]

I just tried on my computer at work and it seems to appear less often here.

But the strange thing is : the window are not displayed properly when they are at the bottom of the screen. The part of the window that is in the bottom don't show.

It seems to be consistent that everything under y=0.92 in relative mode don't show. It is very strange.

Good luck with that....

[scriptkid]

Hi Banania,

I thing i solved the invalidating problem, together with the flickering of the screen. It's much relaxing for the eyes now (The link is the same).

Patrick.

[Banania]

Thanks, I'll try it ASAP.

[scriptkid]

Good to see things are coming along About the only thing I noticed was that the Alpha setting has no effect, and gets reset to 1.0, but you may not have implemented that yet so it might not be a bug.
CE.

Indeed, this wasn't a bug; the numeric value handler was still commented out

Implementing this will be part of the next package.

[CrazyEddie]

Cool. Thought it might be something like that

How are things coming along at the moment? I saw somewhere that you were going to update for the latest code changes, this mostly affects widget names and event names; there may be some work there, but I think the more consistant names we have now are better for all

CE.

[scriptkid]

How are things coming along at the moment? I saw somewhere that you were going to update for the latest code changes, this mostly affects widget names and event names; there may be some work there, but I think the more consistant names we have now are better for all

Hi Eddie!

Good to see you back. Things are coming along nicely. The day before yesterday i modified the Taharez XML file to match the new names, so i'm up-to-date again I hope to release a new package this weekend. Btw i couldn't find an up-to-date xml file in the downloads, is that correct?

Besides i'm fixing some bugs which are mentioned in this thread, before adding new features. But i thought the background-thingy was nice enough to preceed over the fixes

Finally, i'm going to do some research on switching between windows- and taharez look and such, but this depends on how these are related within the system.

Patrick.

[CrazyEddie]

i couldn't find an up-to-date xml file in the downloads, is that correct?

Which file? the scheme file? These are all up to date, though I have switched to using a new naming convention where the generic .xml extension is replaced with .scheme for scheme files, .font for fonts, .imageset for Imagesets, and so on. Check out the Samples/datafiles directory - there's some sample files in there

Finally, i'm going to do some research on switching between windows- and taharez look and such, but this depends on how these are related within the system.

For this I suggest looking into the window type-aliasing features. It would be possible to load a set of widgets (say TaharezLook), and then use some common alias names (you might use aliases such as "Generic/Button", "Generic/Combobox" etc) for the editor. It would then be possible to re-alias these names to refer to anything (like the associated WindowsLook types). There are some things to watch for, like the slider which is vertical in TaharezLook but horizontal in WindowsLook.

Anyway, I know this explanation may not be very clear, but this is certainly possible and it's one of the reasons the aliasing system was put in

CE.

[scriptkid]

Which file? the scheme file? These are all up to date, though I have switched to using a new naming convention where the generic .xml extension is replaced with .scheme for scheme files, .font for fonts, .imageset for Imagesets, and so on. Check out the Samples/datafiles directory - there's some sample files in there

Ok, I found them, thanks

For this I suggest looking into the window type-aliasing features. It would be possible to load a set of widgets (say TaharezLook), and then use some common alias names (you might use aliases such as "Generic/Button", "Generic/Combobox" etc) for the editor. It would then be possible to re-alias these names to refer to anything (like the associated WindowsLook types). There are some things to watch for, like the slider which is vertical in TaharezLook but horizontal in WindowsLook.

Ok, thanks for the hints, i'll know where to search now.

SC.

[CrazyEddie]

Hey scriptkid,

I've been pondering some things and one of them might be of interest or use to you

I am considering some minor extentions to the Property class to provide a getDefault() method, and also an isDefault() method. This way you could check the properties and only write them out if they're not set to the defaults

What do you think?

CE.

[scriptkid]

Hey scriptkid,

I've been pondering some things and one of them might be of interest or use to you

I am considering some minor extentions to the Property class to provide a getDefault() method, and also an isDefault() method. This way you could check the properties and only write them out if they're not set to the defaults

What do you think?

That would be a nice additions, however i already implemented it myself The reason was that otherwise a large bunch of properties got written.

So it's up to you to decide whether to add it

SC.