settings that you want to refer to under the same key (e.g. the apps that
a launcher starts up etc), use
void Epplet_modify_multi_config(char *key, char **values, int num);
And if you want to query for a group of settings, use this:
char **Epplet_query_multi_config(char *key, int *num);
Note that you have to free() the returned array here. The key is internally
encoded into __key__1 for the first string, __key__2 for the second etc.
I put some testing code for this into ConfigTestEpplet.c The epplet will
remember all the command line parameters you give on startup and dump
them.
Also extended E-Mountbox so that the users can now define the patterns
in the device or mountpoint and corresponding icons themselves. Currently
still via the config file, but the dialog is there. Not functional yet,
though.
SVN revision: 1612
(KainX)
Okay, don't kill me. I had to change the API again because it was broken.
Epplet_load_config() now takes no parameters. I also renamed some functions,
which the following command should help you do:
perl -p -i.bak -e \
's/config_data_with_def/config_def/g; s/_config_data/_config/g;' \
<files>
That all goes on a single line, BTW. And replace <files> with the names of
your .c files. You must now specify any defaults by calling
Epplet_query_config_def() instead and passing the default to that function.
I also added the ability to right-justify label text by specifying a negative
x coordinate. See E-Time for a sample.
SVN revision: 989
(KainX)
Alright, I've got the config stuff working as planned. Epplet_Init() has the
same parameters as it used to. If you use config files, make sure to call
Epplet_load_config() AFTER calling Epplet_Init() but BEFORE attempting to
access config data.
Also note the function name changes: Epplet_save_config(),
Epplet_query_config_data(), and Epplet_modify_config_data().
SVN revision: 951
for instance accounting, every epplet has its own directory in
~/.enlightenment/epplet_config/<epplet-name>, transparent config file
handling is provided. Users only need to query for settings and change
settings. Config settings are saved automatically on exit, which
means that users MUST call Epplet_cleanup() before exiting. Every
epplet instance has its own config file. Also added a mechanism for
defining default settings.
Updated all epplets accordingly.
Look at ConfigTestEpplet.c for the details. It shows what instance it
is running as and keeps a record on how many times that instance
has been run in the config files.
SVN revision: 949
Christian Kreibich
Michael Jennings