Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cue Settings Panel #79

Open
wants to merge 4 commits into
base: master
Choose a base branch
from

Conversation

Yinameah
Copy link
Contributor

Rework of my cue setting panel.
CueSettingsWidgets are re-instanciated each time so it's closer to current implementation.

Try to work with an apply button since auto record is really more complicated and need lots of modification on settings pages themselves.

Cue settings are now displayed in a foldable panel.
Almost no modification on existing settings page code

Only implemented on ListLayout.

The area where running cues are displayed is also foldable
Add record mechanism with apply button

A signal as been added in lisp/cues/cue.py so the setting panel
can be notified when changes are done by SettingsDialog
@Yinameah Yinameah force-pushed the info_cue_in_panel_v2 branch 4 times, most recently from d4ca297 to 96d74be Compare April 19, 2017 19:19
Add horizontal splitter for each page, give custom default sizes
Cleaned fold logic and add autoresize when folding
Mapped Return_key to save settings faster
Simple implementation of CueSettingPanel in CartLayout
with a new "intermediate" class for minimal modification

+ dicsconnect cue modification signal when modification comes from
the panel itself
@Yinameah
Copy link
Contributor Author

I've done some serious progress.
It's really usable now, let's call it Beta version.

The use of an Apply button allowed me to be very close of the Dialog Setting mechanism and both work alongside.

Better usability could certainly be achieved, but at the cost of rewriting a lot the settings pages themselves to be more automatically linked to properties. For the time being, it is a good middle path how already enhance the workflow speed by a long shot.

Anyone are welcome to test tracking for bugs...
capture du 2017-04-20 12-36-34

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant