a more efficient way of storing settings (with JV components?)
From: Michal Borsuk (MichalBorsuk_at_sitefinder.___RE'MO-VE__.pl.invalid)
Date: 03/29/05
- Next message: Nicholas Sherlock: "Re: bitmaps in TListbox reappear"
- Previous message: Jamie: "Re: Build in Delphi 5 - VERY slow"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Tue, 29 Mar 2005 16:16:20 +0200
I desinged an app while I was unaware of Jedi components. Since this is
quite a large project, I have settings organized this way:
- all settings stored in a record
- upon startup settings read, restored by code code
- when Options form is called, it's created, settings are filled by code
(reverse process when options form or main form closed)
As you can imagine this is not very flexible nor easy to use. When
there's the need to add something to settings, besides adding e.g. a
checkbox, I have to code in 4 places.
Question:
Is there a way to store a record/struct (or some other unpublished data)
with e.g. JvAppStorage, or for that matter any other component? Or maybe
you'd have some other suggestions how to store program settings? (As
for the visual part, I'd already migrated some properties to
JvFormStorage+JvAppIniFileStorage). I came up with this solution: always
keep Options form open (hide instead of destroying), save settings there
w/JvFormStorage, but isn't that quite memory-inefficient?
I'd be very grateful for any hints. Thanks.
-- Michal Borsuk Advanced Call Manager - a call register and manager. http://acm.sitefinder.pl/
- Next message: Nicholas Sherlock: "Re: bitmaps in TListbox reappear"
- Previous message: Jamie: "Re: Build in Delphi 5 - VERY slow"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|
