First test results and my "wishlist":

• Unrecognized command line options should issue an error message and exit rather than starting interactive mode.
• We should test whether we have write permissions to the system options (file) and if not ...
• (a) issue an error message if a system option should be set (command line)
• (b) gray out (deactivate) system options in interactive mode
• Output of system or user options in commandline mode should also output the option name [1]
• Commandline option --help should be supported (not only -h)
• Maybe add an option to list all system + user options for info (e.g. fltk-admin -l ?)

Notes:

• I tested setting system options w/o root permission and it failed silently.
• My first intuitive test was to use --help which started the interactive mode. :-(
• fltk-admin -l could also support an option name which would list only this option (system + user)
• output of system or user options in commandline mode should also output the respective option name

[1] potential improvement:

$ bin/test/fltk-admin -UVisibleFocus -SVisibleFocus
1
-1

could be changed to something like:

$ bin/test/fltk-admin -LVisibleFocus
VisibleFocus: User: 1, System: -1 

Other than that: my tests on Linux were fine so far (no code review yet). Thank you!

—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.Message ID: <fltk/fltk/pull/560/c1328295150@github.com>