Hey Scott, I have absolutely no idea but I'll email you the developer's address and I'm sure he'd be able to answer accurately.
Slau On Sep 24, 2014, at 4:04 PM, Scott Chesworth <[email protected]> wrote: > Chaps, quick question. Do QuicKeys and Keyboard Maestro use the same > unit/scale/measurement/whatever to specify the location on screen to > be clicked? Essentially I'm wondering whether existing QuicKeys > scripts could be ported over to Keyboard Maestro with a bit of effort > but without needing additional sighted assistance? Just a thought... > > Scott > > On 9/21/14, Slau Halatyn <[email protected]> wrote: >> I started using QuicKeys in 1990 and relied upon it for many tasks. I was >> surprised to see that it even launched under Mavericks. For me, at least, it >> didn't seem to work. >> >> Regarding Keyboard Maestro, it's absolutely accessible. As I mentioned, >> there are just a couple of quirks but, once you get the hang of it, it makes >> complete sense. At the outset, I'd get rid of all of the shortcuts in the >> Global set and disable the other groups. Once you've selected a Group, click >> the Add Macro button. After that, adding an action will bring up a list of >> actions. Clicking on an action and pressing return will add it to the macro. >> The action can then be further modified in any number of ways. Action lists >> can also be edited. >> >> QK certainly had a longer development time but KM does pretty much the same >> thing and it's cheaper, not to mention the fact that it's a current product >> and supported. Anyway, I'm putting my chips on Keyboard Maestro because, >> indeed, QuicKeys will only break down some time in the future. >> >> On Sep 21, 2014, at 4:39 AM, 'Hi' via Pro Tools Accessibility >> <[email protected]> wrote: >> >>> Hey Slau, I was just curious if you feel it's more user friendly from a >>> blind perspective than Quickeys? I posted close to a year ago that I'm >>> still using Quickeys on OS 10.9.3 and being a power user I've been using >>> it for years and never had a problem with it in terms of doing everything >>> not supported by Voiceover. In my limited experience of KM I didn't find >>> it as robust as QK and remember having some trouble navigating around. >>> Some of my QK scripts are over 60 steps long for doing repetitive tasks >>> and my concern has always been what will happen when QK stops working at >>> some point. I'm hoping against hope that you'll tell me it's accessible >>> enough for us to write our own scripts and be able to do most of the same >>> tasks. At this point I can't even do a session without QK because I depend >>> on it for such a variety of things that need a work around. Obviously I >>> use it mostly for getting to positions on the screen VO can't move to but >>> it's even helpful out of the Pro Tools realm. >>> >>> -- >>> You received this message because you are subscribed to the Google Groups >>> "Pro Tools Accessibility" group. >>> To unsubscribe from this group and stop receiving emails from it, send an >>> email to [email protected]. >>> For more options, visit https://groups.google.com/d/optout. >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Pro Tools Accessibility" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected]. >> For more options, visit https://groups.google.com/d/optout. >> > > -- > You received this message because you are subscribed to the Google Groups > "Pro Tools Accessibility" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "Pro Tools Accessibility" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
