Test #1
Folder:
C:\5\QQQ\shortcuts 1_x_178\50501\20101 (a sub-sub-folder actually containing shortcuts)
Path of target: C:\\4(.+) changed to C:\\5\1
Test box checked. Recurse box un-checked.
Results....
New shortcut:
C:\5\QQQ\shortcuts 1_x_178\50501\20101\20101 20102 (correct, same as old, unchanged)
New target:
C:\5\QQQ\images\50501\20101 20102 (does NOT appear to be correct)-nkormanik
OK, I'm confused here - prior to v0.2 it reported
New shortcut/
New target in Test mode.
With v0.2, it reports
Old Target/
New Target, (as you can see in my
post above), because the actual shortcut doesn't get renamed, (as it was doing in the prior version - I naively thought the shortcut would have the same name as the target).
Are you
sure you're using v0.2 ?
Here's a directory setup as you've described above showing that the properties for the shortcut point to the old C:\4\QQQ.... path, (this is using the parameters from your Test #2 but Test #1 also worked):
Here's the Test output with arrows associating between things:
This is the result of execution, the shortcut properties now point to the image in the other directory:
BSM enhancement request 1:
C) DONE! xxxx shortcuts changed; yyyy shortcuts left alone.-nkormanik
See what I can do.
Set up an .ini file containing the last used parameters, and re-use next time program is run.
Easy enough, I'll have it save on close.
UPDATE BSM v0.3 (
here):
- Added: Saves path/regex in an ini file on exit.
- Added: Generates a report when it's finished.
Regarding the report: If nothing went wrong then all it will say is the total number of shortcuts and there was no problem. If something went wrong it will open a log file, (%TEMP%\BSM.log), in your default text editor.
NOTE: BSM works by replacing the existing shortcut by first deleting it, then creating a new one with the new data. The log will show any shortcuts that failed to be deleted or failed to be created, (mark a couple of your shortcuts as Read-Only if you want to see what happens).
Recent Posts
.
