I'm trying to set up 'Ctrl-1' to run the (unsaved) script that I'm editing in TextPad. I'm using TextPad7 on a Windows7 computer.
I've gotten the same thing to run in TextPad5 in the past on both an XP machine and a Windows7 machine, but this time I'm coming up empty.
I have one note from my last go-round with this & it looks like the problem was solved by copying gsl.syn to TextPad's Samples folder and then adding Gsharp as a new tool, etc., but I can't find gsl.syn ANYWHERE.
Does anyone know where to find gsl.syn, or otherwise how to get Ctrl-1 - Run Script RUNNING in TextPad7 / Windows7?
Thanks for any help!
klbatbcl
Running a script using Ctrl-1
Moderators: AmigoJack, bbadmin, helios, Bob Hansen, MudGuard
I managed to get 'Ctrl-1' / 'Run Script' working.
I had installed a registry key using a script that I'd found online, but 'Ctrl-1' still didn't work.
After leaving the problem for a break, I came back and noticed an error in the 'Command' path. I fixed that and IT WORKS!! I'm not 100% sure why, but it works.
Here is the link with the script that I ran to install the registry key:
http://www.autohotkey.com/board/topic/9 ... m-textpad/
I renamed 'TextPad 4' to 'TextPad 7' and changed three key values:
Command => C:\Program Files (x86)\AutoHotkey\AutoHotkey.exe
Parameters => $File
Properties => 000000005680000044000000
It still doesn't show up under Tools/External Tools or Preferences/Tools, but the edited script runs when I press 'Ctrl 1'.
The Command value above also doesn't match what I have on my other Windows7 machine, where Command = ' .. AutoHotkey.ahk', one of my AHK scripts, but 'Ctrl-1' works fine on that machine, I have no idea why. And 'Run Script' IS in the External Tools and Preferences/Tools lists on that machine, so I'm not touching it.
So I'm able to operate, but questions remain. If anyone out there knows what's going on with the above / TextPad's Tools and can explain it to a novice like me who SOMEHOW got 'Ctrl-1' to work, that would be great.
Thanks,
klbatbcl
I had installed a registry key using a script that I'd found online, but 'Ctrl-1' still didn't work.
After leaving the problem for a break, I came back and noticed an error in the 'Command' path. I fixed that and IT WORKS!! I'm not 100% sure why, but it works.
Here is the link with the script that I ran to install the registry key:
http://www.autohotkey.com/board/topic/9 ... m-textpad/
I renamed 'TextPad 4' to 'TextPad 7' and changed three key values:
Command => C:\Program Files (x86)\AutoHotkey\AutoHotkey.exe
Parameters => $File
Properties => 000000005680000044000000
It still doesn't show up under Tools/External Tools or Preferences/Tools, but the edited script runs when I press 'Ctrl 1'.
The Command value above also doesn't match what I have on my other Windows7 machine, where Command = ' .. AutoHotkey.ahk', one of my AHK scripts, but 'Ctrl-1' works fine on that machine, I have no idea why. And 'Run Script' IS in the External Tools and Preferences/Tools lists on that machine, so I'm not touching it.
So I'm able to operate, but questions remain. If anyone out there knows what's going on with the above / TextPad's Tools and can explain it to a novice like me who SOMEHOW got 'Ctrl-1' to work, that would be great.
Thanks,
klbatbcl
I use TextPad to edit AutoHotkey scripts. I've always been able to install a Tool / External Tool in TextPad, called 'Run Script' which would run the script being edited when I hit 'Ctrl 1'. The script did not have to be saved; it just had to be currently open in TextPad. It's a handy & quick way to run and test changes to a script before saving, etc.
Update to my second post: I did not end up getting it the problem fixed. As a workaround, I had written a quick 'Ctrl-1' script in my own AutoHotkey script library that would run the SAVED version of the script currently open in TextPad, and IT was what ran, not a TextPad Tool. So I got fooled again.
I've been getting along / working on everything else, but I would like to get this piece figured out somehow. I don't know why TextPad hasn't just made it part of their program. Running into a problem like this is a real pain!
Thanks again for anyone's help!
klbatbcl
Update to my second post: I did not end up getting it the problem fixed. As a workaround, I had written a quick 'Ctrl-1' script in my own AutoHotkey script library that would run the SAVED version of the script currently open in TextPad, and IT was what ran, not a TextPad Tool. So I got fooled again.
I've been getting along / working on everything else, but I would like to get this piece figured out somehow. I don't know why TextPad hasn't just made it part of their program. Running into a problem like this is a real pain!
Thanks again for anyone's help!
klbatbcl