FLTK logo

Re: [fltk/fltk] New method to return Fl_Preferences location without invoking constructor (#227)

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] New method to return Fl_Preferences location without invoking constructor (#227) zcream May 31, 2021  
 

I'll leave these comments here in case @MatthiasWM decides to look into it. I tried not to bother you, but I still cant figure out runtime prefs. If these are a memory mapped file, they are an excellent way to have an IPC method for FLTK apps. ATM, I have no idea how they are implemented.

\todo (Matt) Before the release of 1.4.0, I want to make a further attempt to write a preferences file smarter. I
plan to use a subgroup of the "runtime" preferences to store data and stay accessible until the application
exits. Data would be stored under ./$(vendor)/$(application).prefs in RAM, but not on disk.

\todo (Matt) I want a way to access the type of the root preferences (SYSTEM, USER, MEMORY), and the state of
the file access (OK, FILE_SYSTEM_FAIL, PERMISSION_FAIL, etc.), and probably the dirty() flag as well.

\todo (Matt) Also, I need to explain runtime preferences.

\todo (Matt) Lastly, I think I have to put short sample code in the Doxygen docs. The test app ist just not enough.


You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.

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'.