#apertus IRC Channel Logs

morning folks!

se6ast1an BAndiT1983 and everyone else: For the visualiser, what is the expected outcome in the below scenario when it comes to BUTTON_UP/DOWN events received?

(this is for T1185 btw)

how is it going?

am fine too

I have a prototype for T1185 but want to see what the expected behavior for the above is

<BAndiT1983 "for this scenario i would assume"> so no BUTTON_DOWN or BUTTON_UP?

maybe just check if release and fire the event, there were discussions about clicking outside in imgui issues somewhere

upon and a click-and-release of Button 1 (both click and release within the Button 1 area), a Button::BUTTON_1_DOWN will be sent, directly followed by Button::BUTTON_1_UP

as you can't avoid click on the real board it should always fire button_up, even if released the button

hmm, now I'm confused :)

"

ah, ok then

would always implement how the real board is behaving, it's still a simulator of some sort

<BAndiT1983 "would always implement how the r"> yes, my thought exactly

1. click and release both within the button area -> BUTTON_X_DOWN and then BUTTON_X_UP in the next itreation

second case wouldn't be possible, as the highlighting should be tested while holding the button down, just fire button up always

no, i mean button up, what i see in the firmware usually, which is still done manually, but will be turned into event handlers and other nice stuff, is the button down which highlights the button in the UI and the action executes at button up

thanks

please try it with button 5 or 6, to see if highlighting is working while you press the button

as the buttons are switched manually for now with switch/case and not event handlers

just to make sure: what you're referring to is still within the context of the visualizer, right? Not the firmware

check MainPage, there you will see the manual intervention, which should be removed by handlers and automatic highlighting etc.

https://github.com/apertus-open-source-cinema/AXIOM-Remote/blob/f5109c4a7b1947ed2c7e4ecfe4e3ea33f08f0539/Firmware/UI/Screens/MainPage.cpp#L90

ah, so what you mean is that visualizer button higlighting will be triggered all the way back from the firmware? (e.g. with callbacks)

understood :)

have fun, see you

BAndiT1983:

please have a look at my fork, and pull to test if needed. I'm waiting for your feedback to iterate on the solution

FYI (1) the knob button is not included in this (2) Ah, and also if you notice unexpected behavior (e.g. when selecting the 'Exit' option in the MENU) this is not linked to the changes. I reverted and the issue exists even without them

you mean the crash on button 11?

I remember I had a few crashes, but also when going into the menu (button 4) and then selecting the "exit" option I got the LCD brightness dialog instead of returning to the main screen

haven't looked at functionality lately, as i'm occupied with a little bit different development right now

oops, the double 10 buttons is my bad

but at the moment it's not behaving like the board, when mouse pressed then "button down should be sent"

yep

great, we can chat about it tomorrow, have to leave for today, work awaits in the morning

yeah, likewise

good night everyone

off for today, good night