Close
Showing results 1 to 10 of 10

Threaded View

  1. #9

    Default

    ~+2::
    ControlSend,,{Shift down}{2 down}{2 up}{Shift up}, ahk_id %wowid1%
    ControlSend,,{Shift down}{2 down}{2 up}{Shift up}, ahk_id %wowid2%
    return

    And for conditionals to getting key states you can simply use:

    ~a::
    If GetKeyState("a","P")
    {
    ControlSend,, {a down}, ahk_id %wowid2%
    }
    Else
    {
    ControlSend,, {a up}, ahk_id %wowid2%
    }
    return

    And nest shift and key required within the required blocks. D & U can still be used. P defines a physical key press. No need to define 2 blocks for up and down. Just test the key state. Longer way would have been to write If GetKeyState("a","P") = 1 .. which means of course true (key is being pressed). If key is not true, then just automatically do else.

    I am truly happy someone is trying to also learn AHK .. I do hope you are using AHK L however. Can be found as a link to their main site. Its the newest version. I have found AHK to be a bit slow on my machine. While AHK L is not. Its a wonderful version.

    I feel the reason most use other boxer tools. Is because scripting becomes daunting to them. Though it gives you a sense of accomplishment, when you roll your own code for your own use. And truthfully compared to all the other free applications around AHK / AHK L. Is far superior, and can do just as well and often times better. Just not everything is so easily found. Google is your friend.
    Last edited by Darkreign11 : 09-21-2012 at 01:44 PM

Posting Rules

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •