[RWP] AutoHotKey A Few HotSpots

Sat Mar 9 16:00:41 EST 2013

The problem  with absolute screen pixel  coordinates, where the top left 
corner of the screen is 1,1, is that as your application gets resized, or 
moved around when you open other stuff, etc, etc, the location of interest 
in your application moves to a different set of absolute coordinates.
However, a system that uses the top left corner of the application, rather 
than the screen, as it's reference is less vulnerable to those kinds of 
shifts.
Likewise with a pluggin.  If your addresses are relative to the corner of 
the plug itself, then you can drag the plug anywhere you want to, and still 
get the same point of interest, because the reference moves in the same way 
as the point of interest does.
HTH

----- Original Message ----- 
From: "Indigo" <33indigo at charter.net>
To: "Reapers Without Peepers" <rwp at reaaccess.com>
Sent: Thursday, March 07, 2013 11:59 PM
Subject: Re: [RWP] AutoHotKey A Few HotSpots

> Jim, when I derive coordinates with my home made screen scraping method; 
> It results in standard resolution X Y coordinates, which I think always 
> starts the pixel count from the upper left corner of the screen, doesn't 
> it?
> How could a button's coordinates not be relative to the upper left corner; 
> where the pixel count begins; even if I begin my search from another point 
> on the screen?
> I've had the issue of Reaper screen coordinates not working in Sonar, even 
> for the same screenreader, don't know why.
> Someday I intend to install a reasonable size and complexity Sonar, like 
> Sonar version 4, which I can get around on, and try to derive coordinates 
> for the same VST synth buttons, then find, if possible, a conversion 
> factor.
>
> I never use Reaper's generic plug interface, even though it works for my 
> hand rolled method of finding buttons, because the more friendly synths, 
> like LinPlug Albino offer some text titles on their native interfaces, and 
> I'd constantly be switching back and forth between Reaper's generic 
> interface and the plug's native interface.
> I think it's the word arpeggiated, or maybe the word ambient;  on the 
> Albino interface that I left click, which drops a list of presets, in that 
> catagory; but then it exposes titles of other catagories, like leads, 
> basses, keys.
> Like all of us, I'm sure; I'll take any clue I can find to get a toe in 
> the access door.
> Indi
>
>
> On 3/7/2013 11:06 PM, Jim Snowbarger wrote:
>> I don't need this to work, but it doesn't.  And, he's in hiding.  Yeah 
>> sure,  quick coords over the shoulder and then voluntary exile.  Just 
>> like a rain soaked ausie.  ... <grinn>
>>
>> Does "click" in AHK terms, mean left click?
>> These coords,  are they relative to the top left corner of the screen?
>>
>>    ----- Original Message -----
>>    From: David P Shortland
>>    To: Reapers Without Peepers
>>    Sent: Thursday, March 07, 2013 12:13 AM
>>    Subject: [RWP] AutoHotKey A Few HotSpots
>>
>>
>>    Hi & Greetings from a drying out Sunshine Coast
>>
>>    Thought I would share this with anyone who may be interested
>>
>>    As I am charting my way thru the  Help files of AutoHotKey and 
>> learning to Script this and that, well mainly for Omnisphere at present, 
>> here are a couple of co-ordinates that may be of helpin REAPER,  with 
>> regards to a Certain Menu not opening with Apps Key & Up Arrow key
>>
>>    These co-ordinates will give access to a menu that will be spoken and 
>> contains settings for Audio & MIDI Inputs & Outputs.
>>
>>    136, 176 is for Trak 1
>>    136, 276 is for Trak 2
>>
>>    Now for those of us who may be a little apprehensive in trying to 
>> write a script to access these co-ordinates,here its is...
>>
>>    Open up Notepad and type these lines as is, or just copy them across..
>>
>>    Numpad9 & Numpad1:: Click 136, 176
>>    Numpad9 & Numpad2:: Click 136, 276
>>
>>    Save this document as AutoHotKey.ahk
>>
>>    Go to the directory where you just saved that script
>>
>>    Double Click on the file and it should ask you with what file do you 
>> wish to run the program?
>>
>>    Navigate to AutoHotKey and voila ... all should be good
>>
>>    Okay, just remember that the resolution on my System is 768 x 1024 , 
>> so one can deduce that if your resolution is different the co-ordinates 
>> will not match.
>>
>>    Now all you have to do when REAPER is open and you have several tracks 
>> in place
>>
>>    Press Numpad9 (hold it down and Press Numpad1 the Menu should open, 
>> make yourselections
>>
>>    Remember that this combination is for Trak 1.
>>
>>    I have also used the Numpad as ReaAccess and REAPER use a lot of 
>> keyboard combinations and this should not interfere.
>>
>>    Oh yes... DO NOT forget to press the NumLock .. it must be ON!
>>
>>    I have only given the co-ordinates for two trax, because I figure if 
>> you want to set up several combinations of In & Outs, just coply one of 
>> the tracks to another place.
>>
>>    Hopefully all will go smoothly... if not...I have left the country and 
>> gone into hiding...
>>
>>    Take care all
>>
>>    David P Shortland
>>    DragonScore Productions
>>
>>
>>
>>
>>
>>
>>
>>
>> ------------------------------------------------------------------------------
>>
>>
>>    _______________________________________________
>>    RWP mailing list
>>    RWP at reaaccess.com
>>    http://reaaccess.com/mailman/listinfo/rwp_reaaccess.com
>>
>>
>>
>> _______________________________________________
>> RWP mailing list
>> RWP at reaaccess.com
>> http://reaaccess.com/mailman/listinfo/rwp_reaaccess.com
>>
>
> _______________________________________________
> RWP mailing list
> RWP at reaaccess.com
> http://reaaccess.com/mailman/listinfo/rwp_reaaccess.com
> 