> Well it depend in the point of view. Lets say plucker's API allow
> other programs to store settings with a name. So later this other app
> could call the stored settings by a name. I would not say that this
> are a mess with the original app. Keep in mind that the [Lissi-Shell]
> section are not change any other thinks in plucker, it is only used if
> your frontend call it.
>
> The same mechanism are used by the "right-click Frontend" thats
> included in the setup (right click in the explorer on a *.html and
> select "convert to Plucker"). Its a Frontend (a simple, but..) and the
> settings it use are stored in the main plucker ini in the
> [CONTEXT_DEFAULT] section.
Hm. I need to ponder this a bit.
[snip]
> Sure if this possible. But i just see that Krayzel use Delphi, so its
> maybe difficult :-)
SetWindowLong and SetParent should do the trick if all fails ;)
> Never Mind was the user want, the _only_ right value for the
> PluckerHome are the Directory were Plucker are installed :-)
>
> You could set a different PluckerHome but then you also need take care
> that a plucker.ini with the right settings are there (include the base
> settings for the image converter tools).
M-hm.
> About the PluckerDir: That the one the user should set. plucker-build
> set this to the working Directory so you do not *need* to set this on
> the command line (so could could save space here). If the user select
> a PluckerDir (eg. C:\Test\Testing) you could add this in the BAT: C:\
> CD\ CD Test\Testing plucker-build.exe ......
Umm. I'd rather read the current path and change it from my program,
not from the batch ;) The batch should call, nothing else. And should
I decide to ditch the batch in favour of CreateProcess at some time
in the future, this would be the only acceptable way.
> Lissi> You can't rely on having plucker or plucker-build in the $PATH,
> it's Lissi> not done during setup. Perhaps it would be a good idea to
> add it?
>
> It's done by put a copy of plucker-build.exe in the Windows directory.
Ouch :( Wouldn't a .lnk have the same effect without keeping multiple
copies around? Multiple copies are a major problem if you ever need
to label or GUID it.
> So you could access from every place without messing with the PATH
> setting. I do not wan't to modify the PATH because the are also a
> length limit :-(
>
> The best you could do are access the Registry key
> Software\The Plucker Team\Plucker\Path
> to read the Plucker Directory and the call:
> <PLUCKERDIR>\plucker-build.exe
I didn't know of the key before you told me :) I'm going to change
that this weekend.
> Well not the command line are limited to 80 chars, only the DOS Box
> are limited to that (and there also enough other bugs here :-( ).
I only looked it up yesterday. You're right, the commandline is
limited to 128 chars, not 80.
> As i started with the Windows distribution of Plucker i also used a
> BAT file to call the tools similar as you do it. But after receiving a
> lot of bug report (because every Windows has its own bug in the DOS
> box) i give up this :-(
So you'd favour CreateProcess and a bunch of settings in the registry?
Dirk, would you please not CC to my personal address? As much as I
like hearing from you, I always confuse the message to answer to :)
Lissi
--
Life ain't fair, but the root password helps.
- BOFH
PGP-Fingerprint:
F119 52A9 A520 B1C5 28B7 BDFE 2B72 9E38 479E 31CC
