In debugging some preferences GUI behavior, I'm wondering about the need for the "Save all preferences" menu option. I say that because, so far, both the path and startup dialogs already send "pd save-preferences" when the ok button is pressed. Also, the audio dialog has the "Save All Settings" button and we really only need to add similar functionality to the midi dialog.
I propose the following: * path & startup dialogs save preferences with ok button (current behavior) * audio & midi dialogs save preferences with ok button (add this) * remove "Save all preferences" button in audio dialog * remove "Save all preferences" menu option as I think this is counterintuitive...
Conceptually I see things like this: * there is a current preference state at all times * the state is loaded from the default location at start * this state can be updated when making changes in the dialogs and hitting the ok button * I can save and load the state to and from external files * I can clear the state
The "Save all preferences" menu option implies there are separate states between the GUI and pd core. As far as I can tell, there currently aren't.
-------- Dan Wilcox @danomatika http://twitter.com/danomatika danomatika.com http://danomatika.com/ robotcowboy.com http://robotcowboy.com/
What about merging all the preference dialogs into one, with tabs?
-- www.paulwrankin.com
On Thu, 20 Jul 2017, at 12:13 AM, Dan Wilcox wrote:
In debugging some preferences GUI behavior, I'm wondering about the need for the "Save all preferences" menu option. I say that because, so far, both the path and startup dialogs already send "pd save-preferences" when the ok button is pressed. Also, the audio dialog has the "Save All Settings" button and we really only need to add similar functionality to the midi dialog.
I propose the following:
- path & startup dialogs save preferences with ok button (current behavior)
- audio & midi dialogs save preferences with ok button (add this)
- remove "Save all preferences" button in audio dialog
- remove "Save all preferences" menu option as I think this is counterintuitive...
Conceptually I see things like this:
- there is a current preference state at all times
- the state is loaded from the default location at start
- this state can be updated when making changes in the dialogs and hitting the ok button
- I can save and load the state to and from external files
- I can clear the state
The "Save all preferences" menu option implies there are separate states between the GUI and pd core. As far as I can tell, there currently aren't.
Dan Wilcox @danomatika http://twitter.com/danomatika danomatika.com http://danomatika.com/ robotcowboy.com http://robotcowboy.com/
Pd-dev mailing list Pd-dev@lists.iem.at https://lists.puredata.info/listinfo/pd-dev
*sigh*
Yes, that's the plan, however it depends on a number of things and is not trivial, mainly due to macOS still being stuck with Tk 8.4 for now. I answered this same request on the pd-list already.
My current suggestion is the pragmatic approach that doesn't involve me spending another week on Pd working on dialogs.
On Jul 19, 2017, at 4:51 PM, Paul Rankin hello@paulwrankin.com wrote:
What about merging all the preference dialogs into one, with tabs?
-- www.paulwrankin.com
On Thu, 20 Jul 2017, at 12:13 AM, Dan Wilcox wrote:
In debugging some preferences GUI behavior, I'm wondering about the need for the "Save all preferences" menu option. I say that because, so far, both the path and startup dialogs already send "pd save-preferences" when the ok button is pressed. Also, the audio dialog has the "Save All Settings" button and we really only need to add similar functionality to the midi dialog.
I propose the following:
- path & startup dialogs save preferences with ok button (current behavior)
- audio & midi dialogs save preferences with ok button (add this)
- remove "Save all preferences" button in audio dialog
- remove "Save all preferences" menu option as I think this is counterintuitive...
Conceptually I see things like this:
- there is a current preference state at all times
- the state is loaded from the default location at start
- this state can be updated when making changes in the dialogs and hitting the ok button
- I can save and load the state to and from external files
- I can clear the state
The "Save all preferences" menu option implies there are separate states between the GUI and pd core. As far as I can tell, there currently aren't.
Dan Wilcox @danomatika http://twitter.com/danomatika danomatika.com http://danomatika.com/ robotcowboy.com http://robotcowboy.com/
Pd-dev mailing list Pd-dev@lists.iem.at https://lists.puredata.info/listinfo/pd-dev
-------- Dan Wilcox @danomatika http://twitter.com/danomatika danomatika.com http://danomatika.com/ robotcowboy.com http://robotcowboy.com/
Also, this is not meant to say "no, won't happen" but more in the line of "we're working toward that". I may have a hybrid solution but that still involves a decent amount of work and testing, so not for this release.
On Jul 19, 2017, at 4:53 PM, Dan Wilcox danomatika@gmail.com wrote:
Yes, that's the plan, however it depends on a number of things and is not trivial, mainly due to macOS still being stuck with Tk 8.4 for now.
-------- Dan Wilcox @danomatika http://twitter.com/danomatika danomatika.com http://danomatika.com/ robotcowboy.com http://robotcowboy.com/
Awesome. The pessimist in me was expecting something like "no, why would you ever want combined preferences".
What's the pathway towards using Tcl/Tk > 8.6 for macOS? Could Pd.app be bundled with embedded Tcl/Tk build from their master branch? A can of what kind of worms will this open?
Fwiw the READMEs in Tcl/Tk master branch refer to it as 8.7 now.
-- www.paulwrankin.com
On Thu, 20 Jul 2017, at 01:00 AM, Dan Wilcox wrote:
Also, this is not meant to say "no, won't happen" but more in the line of "we're working toward that". I may have a hybrid solution but that still involves a decent amount of work and testing, so not for this release.
On Jul 19, 2017, at 4:53 PM, Dan Wilcox danomatika@gmail.com wrote:
Yes, that's the plan, however it depends on a number of things and is not trivial, mainly due to macOS still being stuck with Tk 8.4 for now.
Dan Wilcox @danomatika http://twitter.com/danomatika danomatika.com http://danomatika.com/ robotcowboy.com http://robotcowboy.com/
I'm realizing now that this proposal will not quite work yet as the state loaded from a file with the Load From... menu option is not automatically saved, so the Save All Preferences menu entry will still be needed. This is something we can iron out later on.
On Jul 19, 2017, at 4:13 PM, Dan Wilcox danomatika@gmail.com wrote:
In debugging some preferences GUI behavior, I'm wondering about the need for the "Save all preferences" menu option. I say that because, so far, both the path and startup dialogs already send "pd save-preferences" when the ok button is pressed. Also, the audio dialog has the "Save All Settings" button and we really only need to add similar functionality to the midi dialog.
I propose the following:
- path & startup dialogs save preferences with ok button (current behavior)
- audio & midi dialogs save preferences with ok button (add this)
- remove "Save all preferences" button in audio dialog
- remove "Save all preferences" menu option as I think this is counterintuitive...
Conceptually I see things like this:
- there is a current preference state at all times
- the state is loaded from the default location at start
- this state can be updated when making changes in the dialogs and hitting the ok button
- I can save and load the state to and from external files
- I can clear the state
The "Save all preferences" menu option implies there are separate states between the GUI and pd core. As far as I can tell, there currently aren't.
Dan Wilcox @danomatika http://twitter.com/danomatika danomatika.com http://danomatika.com/ robotcowboy.com http://robotcowboy.com/
-------- Dan Wilcox @danomatika http://twitter.com/danomatika danomatika.com http://danomatika.com/ robotcowboy.com http://robotcowboy.com/
-
Dan Wilcox -
Paul Rankin