CEGUI (Crazy Eddie's GUI) Forums

Hello,

I'm currently utilizing the TaharezLook.imageset / .looknfeel / .scheme where right now I'm just changing the .imageset within CEED to match with my new gui assets. Everything has been working fine mostly so far. However, when I started mapping over the ComboBox & Alternate Progress bar with my custom images things started to not work. For the ComboBox, the ComboBoxList gui pieces are visible, however I am not able to see any text for the choices that are present. Also, for the ScrollBar pieces that are used with the ComboBox, the VertScrollButton pieces are very distorted and out of place. I'm also not seeing any ScrollBarThumb.

Similarly, for my AltProgress pieces, for some reason I am not seeing them correctly when they progress. They appear to be just small pixels.

The biggest difference from the default TaharezLook to my CustomGui is the resolution has changed. I'm using a 2048 x 2048 image, while the original TaharezLook is a 256 x 256. Where my new gui pieces are much larger then the original as well.

Are there any other settings that I need to adjust manually within the .looknfeel to adhere to my modified imageset?

I modified my ComoboboxList pieces to be 32x32 instead of a 75x75 I had, and now I can see the items, but the items are surrounded by too much space of the surrounding image. Is there a way I can reduce the size of these without having to modify the pixel size to be smaller? How do I make the contents area use the surrounding area correctly?



Similarly, the MiniVertScroll buttons appear distorted and too large:


Interestingly the MiniVertScrollThumb is appearing correctly.

I'm messing around in the VerticalScroll bar area in TaharezLook.looknfeel:

I changed the:
<Dim type="Height" ><ImageDim name="TaharezLook/MiniVertScrollUpNormal" dimension="Height" /></Dim>
to:
<Dim type="Height" ><UnifiedDim scale="0.1" type="Height" /></Dim>



I also did the same thing for the MiniVertScrollDown. This does make those buttons appear more correct, however, now it seems that the ScrollThumb doesn't work correctly.

The Thumb is its own widget, thats why it appeared correctly in that one image. Regarding the rest it would be the best for you to look at the actual code of the specific widgets to understand how the areas are used - especially for the thumb. That is all I can say for now, without digging into it deeply.