Hi Dirk & Folks,

thanks for all the positive feedback from many of you...

> - You could pass some environment variables to RunSync.exe
>   - plkr-nonag : set to true and you will not be promoted for an key
>     press. (No need to set the close_on_* ini keys)
>   - plkr-timeout : Set the time in secondes after the DB build time
>     out in all cases. Maybe an good idea for an conduit.
>
>     (Yes i really should write the infos somewhere in the readmes
:-)

Thanks for pointing that out. Will be in 003...

>   - You may could add an Checkbox to run the console mode windows
>     hidden. I'm doing this with by calling the program with create
>     process, by this i get also the return code (<>0 there are an
>     error):

No problem - I just like to see what's crashing on in the bg ;-)

> - You do not need ask the user for the RunSync.exe location, you
could
>   read the Plucker home from:
>   HKEY_CURRENT_USER\Software\The Plucker Team\Plucker\Path
>   Then RunSync.exe are located in this directory.

That solves a lot of issues. I'll also write the INI files into a
subdir of the plucker dir, if it can be found so easily. I didn't have
a look into the registry, which turns out to be a mistake :) .

> - Does writing the ini to the Windir work on all systems (user
>   rights)? Maybe an Plucker Subdirectory in the users directory (the
>   subdir of the Palm SW dir) are an better choice? Or may you could
use
>   an new key in the channel plicker.ini "update_on_sync" (In this
case
>   plucker-desktop could modify this info also from his GUI (Checkbox
>   update on sync) later)?

Good idea - this would eliminate the need to select the DB's to be
synced manually. How far is the development of this GUI from being
stable and distributed?

> - BTW: The rule to get a list of all DB handles are:
>   All subdirs of the Plucker dir that follow this mask: "*.DB" and
>   having an file called "plucker.ini" inside are Plucker Channels.

That would be nicer as I could display a list of check boxes and the
user could just tick them to sync or not. I'd suggest doing it in the
GUI and setting an ini file key for it anyway, then the conduit
retrieves a list of DB's to sync using your method.

Thanks for the input, I'll keep on coding. Especially an installer to
automatically register/unregister the DLL would be nice at the moment,
these zip+batch files are a bit ugly...

Greetings, P

Reply via email to