This was supplied as output by manual panellization in altium

Great, it works!

The place for the draw() method of the checkbox icon is here: https://github.com/apertus-open-source-cinema/AXIOM-Remote/blob/dev/Firmware/UI/Widgets/CheckboxMenuItem.h#L43

Understood and convinced :)

I thought about this quite a bit and think the reason that the ABC layouts are used is that every locale has a slightly different keyboard layout so international corps are afraid of the QWERTY approach not fitting anyone but the UK/US folks.

It's really not a lot of code to do and would save only the framebuffer to file. Just a nice to have feature, like we did it for OC.

Would that really save much time/effort?

The ImageButton is working but I've fixed the implementation so need to make it more flexible.

In T1177#16845, @sebastian wrote:

The structure should allow for different datatypes in the future.

Currently its a dropdown menu of string entries only.

1.
I would like to support integer values as well in the future where just one item appears in the parameter menu and the value changes as the knob is turned.

Can create visual concept if required.

2.
boolean options with checkbox (on /off)
no menu should open here when clicked, just the checkbox checked/unchecked

Well done @BAndiT1983 and @panintended

./example_sdl_opengl3

Screenshot:

I am back to the black screen now.

@BAndiT1983 sure.

latest commits add:

• dimming of background to give visual focus to popupmenu
• automatic resizing - matching the choices
• alignment to right side of menu
• display of current value in the settingsmenu
• parametermenu normally opens "upwards" from the selected entry but if that entry is further up leaving not enough space for the popup the parameter menu is pushed down automatically.

Canon:

Tried and getting OpenGL 2.1 in the terminal output. @panintended Can you check it? No profile worked for me yet, but the order is certainly important.

In T1173#16957, @Ashok wrote:

NOTE: UPDATED LINKS

Reference: https://github.com/apertus-open-source-cinema/AXIOM-Remote/blob/dev/Archive/AXIOM_Remote_Prototype_V01.X/draw.c#L787
The animations start was triggered like this:
https://github.com/apertus-open-source-cinema/AXIOM-Remote/blob/dev/Archive/AXIOM_Remote_Prototype_V01.X/menu.c#L640

The animation itself was handled here:
https://github.com/apertus-open-source-cinema/AXIOM-Remote/blob/dev/Archive/AXIOM_Remote_Prototype_V01.X/main.c#L677

Reference:

Great analysis, thanks. Would check it with the Ubuntu VM. Do you have a fork with a fix for testing?

It appears that the issue doesn't lie in the choice of OpenGL core profile, but rather on the OpenGL attributes being set after the SDL_Window object is created (see also: https://wiki.libsdl.org/SDL_GL_SetAttribute#Remarks).

Found the link which contains the code i've used for generation of linearization array: https://jared.geek.nz/2013/feb/linear-led-pwm

Fixed debug painter, now it is done through strategy pattern.

Automatic fallback through two phase init is probably fit for most machines:

Structure is added, next step is side bar implementation. Here the ButtonBar can be used, like the example which is already added, just in combination with the ImageButton.

many thanks @BAndiT1983 !

fixed with https://github.com/apertus-open-source-cinema/AXIOM-Remote/commit/995dcbafd0fd9e7bc465b21f304694ffcf4fdc94

In T1175#16866, @BAndiT1983 wrote:

We've discussed it and this is a workaround, but we need a proper fix, as i fear that future extensions will add more problems. Still debugging and thinking how to resolve.

We've discussed it and this is a workaround, but we need a proper fix, as i fear that future extensions will add more problems. Still debugging and thinking how to resolve.

In T1175#16864, @metal_dent wrote:

I solved it, should I push?

I solved it, should I push?

I think this is happening because in the MainPage.cpp file we first set the font size then draw the text but in the debugpainter file we're only drawing the text

Hardware looks fine, my output for Intel:

Hmmm, it's looking more and more like a setup-specific issue.

panintended what is your hardware setup (GPU) exactly?

Can you post the output from 'glxinfo | grep OpenGL', please?

Interesting, cannot observe such behaviour on my machine. It has 2 GPUs, Intel and nVidia. Both work, for nVidia i start the app with 'prime-run'.