Hello there.
I unzipped version 2.1.0 build 68 beta over my existing install on my home computer (which previously had build 60 beta) and got a few new bugs when using it to launch some (but not all) programs:
1 : It appears that, if the "Start in" field has the path within double quotes (for example, "D:\steam" ) then when clicking the button, instead of the program being started, I get the following error message:
Error while launching application.
Caractères non conformes dans le chemin d'accès.
That last line would translate back to english into something akin to "invalid characters in path"
I don't have the issue when making a new layout so I guess it's likely to only be an issue for the small niche of people who tried a previous beta where the Start in field was already a thing, or who would perhaps manually create such a button, but I feel that either the error message should be made more explicit, or perhaps the program should either automatically remove or ignore double quotes in that field — after testing, I can confirm they're not needed even if the program must be started in a folder that has spaces.
2 : I had a button with the following parameters:
Image file: <sysroot>System32\conhost.exe;0
Application: <sysroot>System32\conhost.exe
Start in: %userprofile%\desktop
Button Caption:\nCMD
Command Window: Skip
Ignore: Variable Text
With build 60 beta the program did run (albeit it started the program in the same folder where the shortcut to launch CRAP pointed it to start in, instead of the one I had specified in the button's properties), but now it gives me a different error instead (see attachment, the line in french would translate to "invalid folder name").
Removing the contents of the "Start in" field from the button, or making sure it doesn't use environment variables with "%", allows it to work again.
Another little thing: I noticed that, if the button caption starts with "\n" to avoid having the text appear too close to the icon, the "\n" also is displayed in the tooltip while hovering the button. While it's more accurate to have it show, I can't help but think it probably shouldn't be showing in the tooltip. However, it would probably be even better if the user could, under the global button properties, set a minimum spacing between the icon and text, so that there would be less need for "\n" in captions.
-ConstanceJill
1. I have fixed in my local copy to where it should remove any sign of double quotes. (At launch phase)
2. Yeah it cannot handle environment variables like that in beta v2.1.0 b68 and previous but I have researched and made a small change to attempt to parse %userprofile% and others from the "start in" with no additional changes needed by you upon the next update. Also now checks to see if it still contains % after attempting to parse the environment variables and will cancel if still found after parsing what it can.
As for the last bit about caption I cannot tell it the space to use between icon and caption. Also make sure the \n isn't shown in the tooltip in button properties as I think in one beta it added them to the tooltip portion in a minor bug from the drag and drop as well and should be fixed though in current beta version.
Example of #2 when environment variables are parsed and the string still contains some that could not be replaced...
Show Posts
It did take me a few minutes of tinkering to figure it out looking thru options and experimenting since I hardly use that button. Also neat on you being a licensed ham as well.