Thanks for the intense feedback.

Unrecognized command line options should issue an error message

Ah, it did, but I messed up. It's changed back.

Output of system or user options in command line mode should also output the option name

I already added a -v option for that.

Command line option --help should be supported

I just added that

Maybe add an option to list all system + user options

-h already lists all available options. The current settings can now be listed with -L, -LS, or -LU.

I assume and (if not) suggest to create a separate folder for fltk-admin after the test phase

Maybe. We will get the request to disable building it with yet another cmake option. Admins who need it can just use cmake ... --target fltk-admin.

note that on Windows we had to create a separate fluid-cmd

Sigh. I read all the discussions about it. Is that really the only way? Is the rest of the world doing it like that as well?

Should we add a default scheme (name) as another option?

The app understands all FLTK command line options, like -scheme oxy. If we want to do a new default scheme, shouldn't it be in all apps, or actually be in the library?

The current GUI wouldn't scale well if we added more options

Over the last 10 years, two options were added and two were removed. I am not too worried that we will run out of space, but in any case, the internal code is very easy to expand (just a lookup array), and the UI is quickly adjusted. This is btw why giving an unsupported option is generating a warning and no error, so existing scripts can continue to set the known options.

I will add the grading out next. Should be merged tonight.

—
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/c1328315854@github.com>