I need to have two such simple Snippets:
Code:
Basic Setting > Short name for menu > CT#1
Basic Setting > Content > CT#1{Enter}
Advanced Settings > Macro mode
Code:
Basic Setting > Short name for menu > CT#2
Basic Setting > Content > CT#2{Enter}
Advanced Settings > Macro mode
Unfortunately when I use them in my outdated audio editor Sony Sound Forge 7.0 [for the purpose of pasting in a name for a marker on a timeline], then they are parsed - but without the hashtag and what follows them i.e.in both case I get
Quote:CT
instead of accordingly
Quote:CT#1
or
Quote:CT#2
which beats the purpose: because in my audio files I need markers which are both usefully named and enumerated. This truncation happens also outside the editor, e.g. in Notepad; and even if I will kill all other scripts and keys modifiers
So I was willing to use a visually standing out replacement for the hashtag sign but e.g.
Code:
Basic Setting > Short name for menu > CT●1
Basic Setting > Content > CT●1{Enter}
Advanced Settings > Macro mode
Code:
Basic Setting > Short name for menu > CT●2
Basic Setting > Content > CT●2{Enter}
Advanced Settings > Macro mode
set work half-way. And that is because outside of the audio editor they both do work A-OK - but in Sound Forge the >>2<< versions has a conflict with this AutoHotkey snippet of mine:
Code:
#SingleInstance Force
#NoEnv
SetWorkingDir %A_ScriptDir%
#If WinActive("ahk_exe C:\Program Files (x86)\Sony\Sound Forge 7.0\forge70.exe")
+2::
Send {LAlt}
Sleep, 55
Send, pfg{Tab 12}
Send, 1
Send, {Enter}
Sleep 99
return
And I need this code to use >>2<< because it corresponds to the >>Shift + 2<< hotkey that is setup in the propriety program of my keyboard with definable keys [which keyboard I use for faster editing, bypassing repetitive multiple mouse clicks needed for execution of some preset within Sound Forge]
I could of course make this work by changing in that third party program the >>+ 2<< part of the hotkey to some other, but I already have an elaborated set of hotkeys used if various programs, some of which are intertwined with others like in this case. So I cannot just simply replace such one problematic puzzle piece with some other because the whole coherent picture will start to fall and will bite me in the butt later on, because I have other >>Shift + DIGIT<< and >>SOME OTHER KEYS + DIGIT<< hotkeys implemented throughout my system [because it is easier to manage, and debug like in this case, intertwined hotkeys when they are enumerated]
And so:
A] Will the >>#<< bug be fixed?
B] If it will get fixed, will it most likely also interfere with that AHK code that uses >>Shift + 2<< hotkey?
I am using Quick Access Popup 11.6.6 with AutoHotkey 1.1.37.00 on Windows 10 Enterprise 20H2 x64 [10.0.19042]