So they are not normal but I don't think they're worth the effort.
Yes, after stepping through the batches' execution, I was able to trace where the errors where coming from. I agree, it's a simple cost/benefit equation, and if the output is hidden, it's an absolute non-issue. But... (see below)
yaP icon: you cannot modify it, unfortunately. You should use a 3rd party application for this purpose.
Fine, no biggie, there are other ways if only less convenient. Maybe on a future release, you could add a setting to make yaP
assume the icon of the exe its INI points too...
Sigil: thanks for yaP-ping it. It started and run fine here, only some minor things:
- Trolltech registry key (better saying its subkeys) may be used by another applications, so it would be safer not to touch it, or at least not to delete it.
- first I thought something's wrong with the .bat files, but finally found that my PC is slow. I had to use wait=2000 in Sigil.ini
- I haven't tested the dictionary files but there were nothing left in USERPROFILE
- there's an empty Sigil directory left in TEMP for me
After reviewing it, I hit a major snag. Whenever I set the INI option "silentbatch=1", it kind of stops working -- the user_dict file doesn't get copied, and interface options are reset. It looks as if the batches need to open the console window to perform. For the time being, I solved it by not setting that option, resorting instead to postfixing relevant lines with '>nul' and '2>nul', thus redirecting standard output and standard error... it's an ugly kludge, but it works.
I'm aware of the issue with the Trolltech
key; regardless, I thought that if I found one that messed up, it would be a prime candidate to getting portabilized...
And now something completely different... yaP v0.23
I didn't plan to release it today but seeing your unstoppable yaP-addiction I changed my mind
Gee, thanks. What I like about yaP
is its 'quick and dirty' way to make things work -- when everything goes well, a portable is up and running in 5 minutes. Its weak spot is the batch files, which are less than evident when you want to 'push the envelope'... Previously, I had been toying with the idea of using something like GUI4CLI
Note: you have to name your yaP launcher differently than the main exe if you would like to use the new multipleinstance feature. yaP checks applications by their names, so naming them similarly will cause yaP saying "The application is already running". I use ApplicationNamePortable.exe for my launchers.
I do it like this, because I have to attend to several rigs which aren't always in synch -- this way I can just drop the yaPed portable where previously the app was. But thanks for the warning.
One more question: is the comment line "; settings file for yaP v2.1
" at the beginning mandatory? Does it get parsed in any way?