IPrefsObject doesn't load/save XML from ENV:/ENVARC:

[javierdlr]

Hi, using applicacion.library's prefsobjects interface to datatetime.docky.
I'm trying to load/save and XML file from ENV:/ENVARC: with IPrefsObjects->ReadPrefs.

Code: Select all

...
#define LIBNAME "datetime.docky"
..
err = IPrefsObjects->ReadPrefs(dict, READPREFS_FileName,LIBNAME".xml",
                               READPREFS_ReadENV,TRUE, READPREFS_ReadENVARC,TRUE, TAG_DONE);
...

READPREFS_ReadENV - (BOOL) Defaults to TRUE.
READPREFS_ReadENVARC - (BOOL) Defaults to TRUE.

and the same for 'IPrefsObjects->WritePrefs':

Code: Select all

...
#define LIBNAME "datetime.docky"
..
err = IPrefsObjects->WritePrefs(dict, WRITEPREFS_FileName,LIBNAME".xml",
                                WRITEPREFS_WriteENV,TRUE, WRITEPREFS_WriteENVARC,TRUE, TAG_DONE);
...

WRITEPREFS_WriteENV - (BOOL) Defaults to TRUE.
WRITEPREFS_WriteENVARC - (BOOL) Defaults to FALSE.


But it seems it doesn't load/read niether from ENV: or ENVARC: :-/
Using snoopy it just tries to load 'datetime.docky.xml' without any path "assigned".
Am I missing something?
Do I have to 'RegisterApplication()' to use such ENV/ENVARC load/save method?

TIA

[trixie]

@javierdlr

It's possible that READPREFS_AppID (i.e. application registration) is indeed required for the ENV/ENVARC-related tags to function. READPREFS_LastAppDocs and WRITEPREFS_LastAppDocs certainly will not function without an AppID, either.

But the autodoc is so sketchy that one simply cannot be sure

[centaurz]

@javierdlr

For dockies, it's better to use DOCKYGET_DockyPrefs / DOCKYSET_DockyPrefs feature. This way, your prefobject is embedded in AmiDock's own prefsobject, and you can have a separate one for each instance of your docky (in an object-oriented fashion). Check winbar.docky source code on OS4depot.

[javierdlr]

OK thx both, will make some tests and post results ASAP.