Hi, there:
In CELayoutEditorII the Image Property editing seems not so convenient. First thing I've done is locating the resources CELayoutEditorII will use. if I drag a static image on to the screen then go to the Widget properties dock window, editting in the Image column and input something like "set:myImgset image:someImg". If the imageset is not in the resources location I specified, then when I'm going to save the layout file, CELayoutEditorII will NOT writing the image setting into XML file. I should put the images and imageset files into the resources location then CELayoutEditorII will display the image but a messy format which is different with displaying in game (I just put imageset and .tga image file into resources location without any additional scheme or looknfeel files) .
Edit:I just find the reason of displaying image in a wrong format: I use DX Texture Tool to convert a dds file to a tga file. When loaded the converted tga file in Editor, the image is up side down. If I use a converted png file, the image displaying is right. However, in game no difference between using tga file and png file.
Edit:I find CEED just now , I mixed CEED with CELE. however, CEED seems unstable now so I will expect it until official release. I watched the Youtube showcase and I believe it will be a powerful tool for GUI Designing (as I do have some inconveniences while designing my GUI).
CELayoutEditorII Image setting inconvenient
Moderators: CEGUI MVP, CEGUI Team
-
- Not too shy to talk
- Posts: 23
- Joined: Wed Apr 13, 2011 14:54
- Location: Shanghai/China
Re: CELayoutEditorII Image setting inconvenient
CELE2 is not being developed anymore, if you can come up with a patch however, I will commit it.
I first wanted to reuse CELE2 for CEED but I went for a bit different solution so I coded the layout editing in CEED from scratch (it's not finished at all at the moment).
CEED is not unstable (once PySide guys sort out some of the ownership bugs I believe it will be quite stable) but is definitely unusable (I have to experiment and do big changes) at the moment I plan to tag snapshots that should be less troublesome. The goal is to have a snapshot version of imageset editing and layout editing by the end of the month. That however depends on how my profitable jobs go (I have to eat and CEED earned me exactly $0, people don't like to donate ), university chores and some other variables (like whether portal 2 sucks or not )
I first wanted to reuse CELE2 for CEED but I went for a bit different solution so I coded the layout editing in CEED from scratch (it's not finished at all at the moment).
CEED is not unstable (once PySide guys sort out some of the ownership bugs I believe it will be quite stable) but is definitely unusable (I have to experiment and do big changes) at the moment I plan to tag snapshots that should be less troublesome. The goal is to have a snapshot version of imageset editing and layout editing by the end of the month. That however depends on how my profitable jobs go (I have to eat and CEED earned me exactly $0, people don't like to donate ), university chores and some other variables (like whether portal 2 sucks or not )
Return to “Official Unified CEGUI Editor Tool (CEED)”
Who is online
Users browsing this forum: No registered users and 3 guests