sgp wrote:Version 1.10 beta 4 does not crash anymore when I create a link to xx.gif !
Yes, the crash happens when NiftyLink (or TC itself) calls the function
CanYouHandleThisFile of a packer plugin, which has a bug in this function. NiftyLink now does not call this function during creation of a link anymore.
sgp wrote:However it does crash (your handler nicely catches the exception) when I execute the link. The error message points to the culprit plugin: wcx\CHMDir\CHMDir.wcx (invalid memory access).
What the next move now? Do I need to uninstall CHMDir.wcx?
I think it depends. I for one keep using the buggy plugin "InstallExplorer", because it works fine with files for which it was built (EXE and MSI setup programs), and I never encountered a crash in "real life use". The only crash that I encountered was with the test file "xx.gif", which consists of a line break. The best would be asking the plugin author to fix the bug.
sgp wrote:Juergen wrote:
New:
Checkbox "Use name of target drive" now shows the name (if existing) in a tooltip.
I checked the box and now I can see the volume label in the link file, but I see no tooltip when I hover my mouse over the link file. Do I need to enable/do something else to display tooltips?
Tooltips for the NiftyLink
files can be displayed by the "Text Line" plugin. What I added was a tooltip for a
checkbox in the dialog for creation of new links. On Windows 7 the tooltip appears upon mouse-over and disappears after clicking the checkbox. If you move the cursor away from the checkbox and back again, the tooltip re-appears. That's normal Windows 7 behaviour. However, I'll change that in the next version.
sgp wrote:At some point in this thread you wrote that file searches that consist of blank separated wildcards need to be quoted
No, this seems to be a misunderstanding. Only if a single pattern contains a blank, then this pattern must be enclosed in double quotes (so that NiftyLink knows that this particular blank is part of the pattern, and is not considered a delimiter between different patterns). I think that TC does not even require this, but doing it this way is straightforward, and I currently don't want to make dozens of tests and to spend much, much time, in order to find out how TC knows the difference between a blank that is a separator and a blank that is part of a pattern, without using quotes.
If you still have mismatching patterns, then I'll have to do a detailed investigation. For that I need exact copies of the respective entries in your INI file.
Regards, Juergen
//last edit: 2012-06-18