Do away with Qt signals #4

New issue

Open

opened 2025-01-22 14:27:09 +01:00 by thibaudk · 0 comments

thibaudk commented

2025-01-22 14:27:09 +01:00

(Migrated from codeberg.org)

the initial design "piggybacked" on the official score UI. This presents several issues:

Interactions on hardware have no effect when the the view differ on the UI (if a different interval is in full view)
Nothing works in --no-gui mode (related to #3)

Current efforts have replaced the used of the "requestHeightpercentage" signal for moving intervals. Instead, the "recursive_change" function makes use of "setHeightPercentage" directly, and propagates the change to all relevant models.

Setting the date of timesyncs, events, and intervals is currently being worked on in a similar way.

This end up looking a lot more like a rewrite of the interface than originally intended.

Their may very well be a better way of achieving the same goal, but it turns out to be quite a interesting excise anyway, if a little tedious.

the initial design "piggybacked" on the official score UI. This presents several issues: - Interactions on hardware have no effect when the the view differ on the UI (if a different interval is in full view) - Nothing works in --no-gui mode (related to #3) Current efforts have replaced the used of the "requestHeightpercentage" signal for moving intervals. Instead, the "recursive_change" function makes use of "setHeightPercentage" directly, and propagates the change to all relevant models. Setting the date of timesyncs, events, and intervals is currently being worked on in a similar way. This end up looking a lot more like a rewrite of the interface than originally intended. Their may very well be a better way of achieving the same goal, but it turns out to be quite a interesting excise anyway, if a little tedious.