On 8/26/21 2:28 PM, Dan Wilcox wrote:
Also tangentially, I would also bring up the handling of some of these flags which affect the state: using -verbose also sets the verbose setting which is then saved with the user settings. I find this annoying as I would rather have the command line flags like this be *temporary* and not affect the actual setting itself. To me changing the value directly in the GUI should (as it does now). I believe I opened an issue about this already.
what exactly is the user-case where this becomes a problem?
i don't have a problem with this: 1. start with clean preferences (defaulting to "verbose: 0") 2. launch Pd with "pd -verbose" - this will give you verbose output as expected 3. open the (Path) preferences - note that "verbose" is enabled 4. save the preferences 5. quit Pd 6. launch Pd without any cmdline flags: "pd" 7. due to the preferences, Pd will now give you verbose output
i think this is not a big problem, as the preferences panel you saved showed "verbose" (and you could have unticked it). i actually like it, that i get a feedback whether "verbose" is in action or not (regardless of whether they are saved or not)
otoh, this is a bit annoying: 1. start with clean preferences (defaulting to "verbose: 0") 2. launch Pd with "pd -verbose" 3. open the *Audio settings* 4. save the preferences 5. quit Pd 6. launch Pd without any cmdline flags: "pd" 7. due to the preferences (that were saved when just storing the audio settings), Pd will now give you verbose output
so you never really had a chance to notice that you were saving the "verbose" flag as well.
i think rather than complicating the code with having temporary/unsaveable flags, a better solution would be to (finally) unify all preferences in a single dialog. so even when interacting with the audio settings, it is clear that you are actually working with *all* preferences.
https://github.com/pure-data/pure-data/issues/516
gfmasd IOhannes