Page 1 of 1
Drop to catalog script question
Posted: 25 Apr 2012 15:04
by LittleBiG
What is the value of <get drop |> if I click on the catalog script instead of dropping something to it? (On my XP I was rewarded with a blue death...)
Is it possible to run separate scripts on clicking and on dropping? Or to disable clicking on droppable scripts?
Re: Drop to catalog script question
Posted: 25 Apr 2012 15:46
by admin
blue death? Never seen blue death on XP since I have it (2002).
Anyway, what's that script? No blue or other-colored death here when clicking <get drop> scripts.
Re: Drop to catalog script question
Posted: 25 Apr 2012 19:12
by LittleBiG
admin wrote:blue death? Never seen blue death on XP since I have it (2002).
Anyway, what's that script? No blue or other-colored death here when clicking <get drop> scripts.
I think, not XY is fully responsible for that. Because clicking on the script, the blue screen says nwfs.sys causes the problem. As far as I know, this is the part of Novell Client application. It would be really hard to test... On win7 is ok, I added a check to my script whether <get drop |> is empty or not. If yes, script is not running. I will check on WinXP again, which line cause the breakdown.
Code: Select all
//moving to folder, name of catalog example: Drop To Pendrive:: K:\Carried_docs
if (<get drop |> == ""){
status "Nothing to do" , , "alert"
}
else {
$ut = gettoken(self("caption"), 2, "::", "t");
if (exists($ut) >= 1) {
moveto $ut, <get drop |>;
}
else {
msg "This path doesn't exist!";
}
}
Re: Drop to catalog script question
Posted: 26 Apr 2012 08:57
by admin
No problems with the script.