FLTK logo

Re: [fltk/fltk] Moved global FLTK options into new app fltk-admin (PR #560)

FLTK matrix user chat room
(using Element browser app)   FLTK gitter user chat room   GitHub FLTK Project   FLTK News RSS Feed  
  FLTK Apps      FLTK Library      Forums      Links     Login 
 All Forums  |  Back to fltk.issues  ]
 
Previous Message ]New Message | Reply ]Next Message ]

Re: [fltk/fltk] Moved global FLTK options into new app fltk-admin (PR #560) Albrecht Schlosser Nov 27, 2022  
 

The app understands all FLTK command line options, like -scheme oxy.

That was not what I meant. Sure, it's good to know that you can use it for this app as well.

If we want to do a new default scheme, shouldn't it be in all apps, or actually be in the library?

I meant to add a new default scheme as system and user preference - just like all the other options. Changing the library to use another default is independent of setting a system or user preference. We can do this, but since the scheme is a matter of taste it should IMHO be a preference (aka option) users can set for themselves and/or the system manager for the system. This would give the following precedence (lowest priority first):

  1. Library default, currently 'none' or 'base', lowest priority. I don't think we need to change this.
  2. System default set with this app by an admin.
  3. User default set with this app by the user.
  4. Environment variable FLTK_SCHEME: overrides the default set in options above.
  5. Commandline option -scheme of program invocation: almost highest priority, overrides environment variable.
  6. Hard coded Fl::scheme("...") in program: should really be avoided because it would override everything.

All points except 2. and 3. exist already, points 2. and 3. would be added by such an option in this app. If all user programs are coded correctly, i.e. using Fl_Window::show(argc, argv) so the commandline works and not using a hard coded scheme (6.) then users can set their preferred scheme and forget about it.

Environment variable FLTK_SCHEME (4.) and the commandline option (5.) should only be used for special cases, for instance testing. The environment variable is used in test/demo to set the selected scheme for all launched test programs.

Note that points 1. - 5. would all be implemented in the initialization part of the library and would not require code in user programs.


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

Direct Link to Message ]
 
     
Previous Message ]New Message | Reply ]Next Message ]
 
 

Comments are owned by the poster. All other content is copyright 1998-2024 by Bill Spitzak and others. This project is hosted by The FLTK Team. Please report site problems to 'erco@seriss.com'.