Maybe an additional -loglevel which allows you set the level explicitly? -verbose to me would set the log level to verbose overall & -noverbose would set it back to the default.
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 wirh 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.
On Aug 26, 2021, at 12:00 PM, pd-dev-request@lists.iem.at wrote:
with the latter in mind, we might even use multiple "-noverbose" flags to lower the verbosity (at least of the stderr) below post() - so that only errors would be visible.
-------- Dan Wilcox @danomatika http://twitter.com/danomatika danomatika.com http://danomatika.com/ robotcowboy.com http://robotcowboy.com/
On 8/26/21 2:28 PM, Dan Wilcox wrote:
Maybe an additional -loglevel which allows you set the level explicitly? -verbose to me would set the log level to verbose overall & -noverbose would set it back to the default.
that might work, but...
do "-loglevel" and "-verbose" act on the same internal state? because, right now, the two are kind of separate, and it's slightly convoluted to separate them (given that with "-verbose" you get additional *error* messages).
i think having them act on the same internal state is a bit redundant and confusing (what is reported with "-verbose -loglevel 3 -noverbose"?)
otoh, if they are separate (like what we have right now in the Pd-GUI) this might work (better?). specifying "-loglevel 1" in "-stderr" mode would only print out messages up to ERROR. when printing to the Pd-console, specifying "-loglevel 4" would set the pulldown menu to "4 all", but not enable verbose printout (like: showing how patches are searched). how would that interact with the GUI-preferences that currently save the loglevel of the Pd-console? (this is obviously related to your other question about persistent/temporary settings)
gfmadsr IOhannes
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