CEGUI (Crazy Eddie's GUI) Forums

Hi there,

I'm opening a new topic to get some hints about creating a widgets that will a mix between a button and a progressbar.

I'll explain: The widget will be a standard button but will visually display a cooldown once clicked and in the disabled state.
I'd like to display the cooldown by a grayish non opaque progress image over the button that will diminish until the cooldown is over.

I thus wondered what would be the simplest (and reusable) way to do it. Is it possible for instance to mix the button and progressbar widgets type, or wrap them in a mother button widget for instance?

Best regards,

Just a question upfront: do you already know how to do the opaque-image thing (e.g. in a regular progressbar)? Is that part of the question?

Just a question upfront: do you already know how to do the opaque-image thing (e.g. in a regular progressbar)? Is that part of the question?

I was thinking about using a color property and setting the alpha part to less than 256 <-> FF.
My actual question is indeed how to mix the button and the progressbar features.

Bertram wrote:

Just a question upfront: do you already know how to do the opaque-image thing (e.g. in a regular progressbar)? Is that part of the question?

I was thinking about using a color property and setting the alpha part to less than 256 <-> FF.
My actual question is indeed how to mix the button and the progressbar features.

That would have been my suggestion.


From what I understand you want the classic "skill-with-cooldown" type of widget, as present in a lot of games of all genres. This would be a great addition to CEGUI!

I think all you need is the basic scrollbar look and behavior that consist of the image above with transparency + image underneath that stays static. This would have to be amended with an extra state in the look that does not include the overlay and is merely for the pre-pressed state. This has also to be reflected in the logic then.

I might be missing something there, not sure. Feel free to post code and I will look at it and we can discuss.

Ident wrote:From what I understand you want the classic "skill-with-cooldown" type of widget, as present in a lot of games of all genres. This would be a great addition to CEGUI!

Yes, exactly the kind of thing I'm trying to achieve.

Btw, I've witnessed that exact widget in Torchlight II, which is using cegui 0.7.x.
I've unpacked their data using modding tools and I haven't found anything in the looknfeel concerning such widgets.
I guess they are using some kind of trick both in code and in their layout but I couldn't be able to read the layouts due to strange encoding issues.

But there is hope.
Maybe they created a child widget in a button and are changing its area with the code? I'll check that possibility and tell you.

Child widgets are always a possibility and its easy to do. But clearly it is not as self-contained and nice as having a full widget doing that entirely on its own. Creating a new widget is the clean way to do it. So I suggest doing that instead of however they might have hacked it. Is their source code even open?

I will help you create this widget, if I was you i would start off with the scrollbar stuff available. Imo the scrollbar should btw not fill up itself but require updates from the outside in regards to its percent value. Otherwise it becomes kind of messy and out of control. Given that fact it is really just an issue of how to display stuff (similar to how it is with the scrollbar) and for that basically you just need the two states (one represents a button, the other the scrollbar).

Hey,

Child widgets are always a possibility and its easy to do. But clearly it is not as self-contained and nice as having a full widget doing that entirely on its own. Creating a new widget is the clean way to do it. So I suggest doing that instead of however they might have hacked it. Is their source code even open?

True. The source code isn't open, but most of their data is, explaining why I could have a look at their look'n'feel file. (I wouldn't want to do reverse engineering here anyway.)

I will help you create this widget, if I was you i would start off with the scrollbar stuff available. Imo the scrollbar should btw not fill up itself but require updates from the outside in regards to its percent value. Otherwise it becomes kind of messy and out of control. Given that fact it is really just an issue of how to display stuff (similar to how it is with the scrollbar) and for that basically you just need the two states (one represents a button, the other the scrollbar).

I'll gladly have a go at this one. Thanks for the advice.

Yet, I must think of a short-term solution at the same time. That's why I'd rather create a parent widget with both children for now as IMHO it will work while being somewhat hackish.
Then, I'll create a new widget for v0 based on your advice. (Is it ok if I base the future widget against v0?)

Best regards,

Base it against whatever you want, it won't break ABI. v0 is fine imo.

If you use a parent&child window as workaround, then remember to set the child window to pass all mouse inputs through to the parent so that all clicks on the "scrollbar" will be registered. Otherwise it may "eat" clicks. After all the scrollbar part is just for presentation.

Hey again,

I wanted to say we found a simple way to fix that!

Here is how:
Not mandatory, but for our own use, in the look'n'feel, we adapted the progressbar lnf part to accept a progressbar custom image parameter: 'ProgressImage'




The actual how is here, in the layout file.
We added a progressbar within the image button:

Note that the area of the progressbar was adapted to avoid showing its borders here.

And voilà !!