Pretty sure I saw this somewhere in the forums once where AHK could be used to positionally click on the infoline description (so long as your Window position is consistent).
Anyone have this?
edit
@ggmanestraki you seem to know how to do this? maybe I can borrow some of your script?
Let’s start from here. I assumed 1920x1080, Status line off.
As long as the main project window is in focus, pressing V will take you to the first field of the Info line. You can tab to go to the next field. (I chose V because it’s not taken by default.)
And steve’s got the easiest solution. Even though I went through the 10.5.20 key commands one by one in the summer, I fail to remember even half of them.
The script does like the key command, except it can’t follow if you activate the status line. Then it will misclick.
Do you want an extra tab baked in so you go to the second info field directly?
WinKey+E (WinKey hence AHK script already in use) (which I’ve now assigned to Edit Info Line)
and then Tab
and then have all this AHK be a shortcut key in itself, say WinKey+Alt+E
Is that possible?
edit
I guess AHK could also be used to cue entry fields in the Project Logical Editor as well, in regards to renaming/append/prepend PLE scripts… damn… down the AHK hole I go…
Look for the simplest way for each
Note that if you use clicks from ahk, this will break under many conditions. Finding images (another popular attempt) in ahk is also pointless, as you’ll be forever editing to adapt to any change in the UI.
in the ahk script just (your keystroke for Edit Info Line)
tab
tab
And then make sure you never change the info line config.
If I were you, I’d avoid adding modifiers to the Winkey combinations. It doesn’t work as easily as any other +^! combination, because it’s a special case.
You can add sleeps and sends as you wish to modify a hotkey. For example, if you have assigned the Play button to edit the info line, you can use v to send the other command.
v & 1:: do one thing
v & 2:: do another thing
v & 3:: do yet another thing
but v will not do anything on its own.
Generally, I assign things to ahk so that they are invisible to Cubase, OR make them work only#IfWinActive, so that I don’t mess with Cubase’s assignments.
I’m not %100 sure what you’re asking… But I think you’re asking why I didn’t just create a new command (or use an already existing one?).
I’m pretty much out of standard keybinds without AutoKey giving me the WinKey. Wanted to use ‘E’ for edit info line, so WinKey+E. Figured to edit description/2ndfield, adding ‘Alt’ made sense and easy to remember.
Also I believe ^!i{tab} would be ctrl+alt+i+tab all at once, which would not initiate the standard OS tab protocol but maybe I’m wrong on that.