-
Notifications
You must be signed in to change notification settings - Fork 34
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
A "i'm doin stuff' screen #1159
Comments
Nice UI might be to have a progress throbber in header which you could click then it says what it's doing. like in BWS, say. |
Ahh I was thinking modal but yes both modes would be lovely |
Modal might be annoying... |
I get that, but right now dropping a bitwig multisample onto a part and having nothing happen for 7 seconds is also annoying! So I was thinking of something to indicate loading is happening We could also replace the select-multi dropdown with a progress-indiciator or a million other things. But the trick is to get the messages back and forth and hooked up to something, and then we can draw it some way as step one. |
Per surge-synthesizer#1159 we now at least have a serialization thread message which the engine can send to the UI with an open/close/update type semantic. We send the messages from SF2 load but we don't do anything with them other than a SCLOG_ONCE for now. Just some progress to get in the codebase before I close my laptop.
Per #1159 we now at least have a serialization thread message which the engine can send to the UI with an open/close/update type semantic. We send the messages from SF2 load but we don't do anything with them other than a SCLOG_ONCE for now. Just some progress to get in the codebase before I close my laptop.
Thinking about #1157 we have some actions which are long time on the serial thread but don't need to block the ui.
For instance, loading an entire big SF2 with all its samples
Would be nice if in addition to the synchronous edge at the thingy in #1157 we had a 'doing stuff' screen so
so then sf2 load could at least say you are doing it and when you are done.
The text was updated successfully, but these errors were encountered: