On 06.09.20 18:20, [email protected] wrote:
But if the UI has to poll a shared object (via a lock..) with a high
frequency,
then we will be bound to have new problems. The event eliminates the
polling.
As i see it, the problem of the event queue is just the code size,
whereas the problem with the
shared state is an architectural problem which might bring up other
issues.
What if we add a little bit more structure to the event queue by
adding a "buttonPressed"
action where the parameter is interpreted as a bitfield? Should we
discuss this topic
in person via jitsi or sth. similiar? I'm still not sure if i'm
missing or misunderstanding
something :)
I see. Yes, this might be a much better solution. Maybe a more complex
event type like Event(GUI_component, specific part/action, value)?
Anyway. I would start implementing the new OSC commands using the
(classic) EventQueue and we can think about the Event stuff at some
later point in time.
All the best,
Phil
_______________________________________________
Hydrogen-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/hydrogen-devel
