GUI

Help!
I can't do the image button, because the ImageMap struct member of the guiButton defined const, so I cannot assign a value for it runtime.
What do you suggest?

FDR wrote: Help!
I can't do the image button, because the ImageMap struct member of the guiButton defined const, so I cannot assign a value for it runtime.
What do you suggest?

What are you trying to do?
you want an image to change when you press it, or to only do an action when an image is pressed?
I was planning to support the latter case by defining a screen-region that when clicked executes a callback. If you want to be able to dynamically change an image, that is somewhat more challenging. I currently do it by deletingthe old object and replacing it with a new one.

I want to make an image button, like an icon.
Based on the button struct, which has everything for it, but would make a different create function, which instead of the button type gets file name and size parameters, like an image control does.
But I can't fill the buttons ImageMap part with this data, because it is defined const...

EDIT: Sorry, I've misunderstood you question! So I want the latter case only...

So, we are running again...

I have checked in a complete rearrangement of the mixer pages!
Now it is much more logical for me.
(Especially after you have enlighten me about the min/max values.)
All the controls are in the order they shoul be set, or at least in which they effect the output.

FDR wrote: I want to make an image button, like an icon.
Based on the button struct, which has everything for it, but would make a different create function, which instead of the button type gets file name and size parameters, like an image control does.
But I can't fill the buttons ImageMap part with this data, because it is defined const...

EDIT: Sorry, I've misunderstood you question! So I want the latter case only...

...or should we add every icon as a new button type?

No the ImageMaps are only for standard GUI primitives. I will checkin code that provides the capabilities you want shortly.

I've committed pressable labels and pressable images now.
Edit:
On the main page the icon and the model name will both go to the load/save page. this is just an example, we probably don't want them both to gothere, but it shows how it works.

And I've merged your changes. Very Nice!

I had to completely rewrite the keyboard widget so it could support buttons. It should be basically working now (both with buttons and the mouse) with mostly the same features it had. the caps button behaves more like you'd expect now.

Let me know if you see any regressions. The new code should make it possible to support a pure-numeric keyboard. I'll work on that next.

Ok, the fixed-id now uses a number-only keypad.
The listbox has button support, but it isn't very good (I used left/right for the scrolling)
I also fixed it so you can change mixer-type without resetting the selection.

PhracturedBlue wrote: Ok, the fixed-id now uses a number-only keypad.
The listbox has button support, but it isn't very good (I used left/right for the scrolling)
I also fixed it so you can change mixer-type without resetting the selection.

About the numeric keypad's navigation:
- from 8 the up goes to 4;
- from 0 the up goes to 7;
- from 9 the up goes to 5;
- from 9 the down is not clear, where it goues to;
- can't select done.

EDIT:
Can the list box selection include the scrollbar too? They form one control together.

I saw you failsafe control.
It took me a while to turn it on!

FDR wrote: About the numeric keypad's navigation:
- from 8 the up goes to 4;
- from 0 the up goes to 7;
- from 9 the up goes to 5;
- from 9 the down is not clear, where it goes to;
- can't select done.

It should be much more intuitive now.

EDIT:
Can the list box selection include the scrollbar too? They form one control together.

No, that will be somewhat difficult as they are separate gui objects.

I think we do need different icons for these toggle-able spinbuttons. That would make it clear when they can be pressed or not.

PhracturedBlue wrote: I think we do need different icons for these toggle-able spinbuttons. That would make it clear when they can be pressed or not.

Yes indeed.
I've just made the reverse clickable too...
Ckecked in.

PhracturedBlue wrote:

FDR wrote: About the numeric keypad's navigation:
- from 8 the up goes to 4;
- from 0 the up goes to 7;
- from 9 the up goes to 5;
- from 9 the down is not clear, where it goes to;
- can't select done.

It should be much more intuitive now.

Better, but still hard to select done:
- from del the down goes to 0;
- from done the up goes to 9...

PhracturedBlue wrote:

EDIT:
Can the list box selection include the scrollbar too? They form one control together.

No, that will be somewhat difficult as they are separate gui objects.

OK, not a big deal...

FDR wrote:

PhracturedBlue wrote: I think we do need different icons for these toggle-able spinbuttons. That would make it clear when they can be pressed or not.

Yes indeed.
I've just made the reverse clickable too...
Ckecked in.

Ok, i merged it. i also just added support for SPINPRESS buttons. They aren't used yet though.
you can create spinp32.bmp, spinp64.bmp and spinp96.bmp
we can then switch the controls over to use FILE_SPINPRESS64 etc where necessary to use them.

FDR wrote:

PhracturedBlue wrote:

FDR wrote: About the numeric keypad's navigation:
- from 8 the up goes to 4;
- from 0 the up goes to 7;
- from 9 the up goes to 5;
- from 9 the down is not clear, where it goes to;
- can't select done.

It should be much more intuitive now.

Better, but still hard to select done:
- from del the down goes to 0;
- from done the up goes to 9...

yes, that is known. I'm not sure yet how to fix it without coding every transition though.
For now the rule is that when switching rows, it will always select the closest numeric/alpha button, and will never select the 'special' del,done, caps, ... buttons.

PhracturedBlue wrote: Ok, i merged it. i also just added support for SPINPRESS buttons. They aren't used yet though.
you can create spinp32.bmp, spinp64.bmp and spinp96.bmp
we can then switch the controls over to use FILE_SPINPRESS64 etc where necessary to use them.

Checked in spinpress bitmaps.