Close
Showing results 1 to 10 of 35

Hybrid View

  1. #1

    Default

    What does HKN say when you try to send the key from the slave?
    Blog : Herding Khats
    Team : Kina - Çroaker - Messkit - Lìfetaker - Wìdowmaker
    Newbie Guides : Multiboxing Vol. 1 - Multiboxing Vol. 2 - HotKeyNet - Jamba
    The Almighty Lax made a liar out of me, apparently I DO get prizes for it.
    *Commences Wielding the Banhammer like there's piñatas up in here and I'm Lady Thor*

    _ Forum search letting you down? Use the custom Google search _

  2. #2

    Default

    The If-statements in your <Hotkey NumPad1> are asking which WoW has the focus on the local PC.

    But one of the WoWs is running on the remote PC. It never has the focus on the local PC. Therefore, one of the If-statements in your hotkey can never be true and it can never execute.

    If you want HotkeyNet to do something conditionally based on conditions on the remote PC, you need to load a script on the remote PC. Put a hotkey in that script with the appropriate If-statement. Then trigger that hotkey from the local PC with a second hotkey definition that includes <DoHotkey ...>.

    P.S. Each of your machines has its own active window (a window that has the focus). Input Director (like all KM programs) disguises this fact from you by making it appear that there is only one active window for both machines. But really there are two active windows at all times, one on each machine. You may need to take this into account.
    Last edited by Freddie : 02-03-2011 at 02:58 AM
    �Author of HotkeyNet and Mojo

  3. #3

    Default

    Okay, that makes sense. I was thinking that might have been the problem after I posted this but I wasn't sure what to do about it. I wasn't aware I could load a script into the slave client. I'll mess around with it some more tomorrow and post back the results. Thanks for the input.

  4. #4

    Default

    You can load scripts into any copy of HotkeyNet and press hotkeys on any keyboard, but you probably don't need to bother.

    If you can assume that when the local WoW's not active, the remote one is, you can just replace the second If with Else.

    And you don't need to rename the WoWs. Renaming is only necessary to distinguish multiple instances on the same PC.

    Code:
    <Hotkey Numpad1>
       <If ActiveWinIs "World of Warcraft">
           <SendLabel ....>
           <Key Numpad1>
       <Else>
           <SendLabel ....>
           <Key Numpad1>
    Last edited by Freddie : 02-03-2011 at 06:02 AM
    �Author of HotkeyNet and Mojo

  5. #5

    Default

    Yeah, I'm aware of that. I did the renaming because I actually run 4 toons on one box and 1 toon on the other box. So I just rename them all WoW1-WoW5 so I know which window is which. I was only doing 1 on each box until I get this issue worked out. So using "Else" will not work for me because I have 3 other toons.

  6. #6

    Default

    Quote Originally Posted by Nomahd View Post
    I was only doing 1 on each box until I get this issue worked out..
    You must be a programmer.

    One of the things I've learned from supporting HotkeyNet for four years is that it doesn't occur to people that the way to write complex scripts is to start with something simple. After the simple thing is working, add to it and make it more complex.

    It seems like the most obvious thing in the world, but it just doesn't occur to people. It never ceases to amaze me. They will post 200-line definitions with embedded templates and includes and say, "I can't figure out what's wrong. Help!"

    Well of course they can't figure out. The definition is too complicated. I can't figure it out either.
    Last edited by Freddie : 02-03-2011 at 06:22 AM
    �Author of HotkeyNet and Mojo

  7. #7

    Default

    Quote Originally Posted by Freddie View Post
    You must be a programmer.
    Guilty.
    I've dabbled in programming as a hobby since I got my first computer (Commodore 64) like 20 years ago. It seems that no matter how much you know about computers there are always new things to learn, and new problems to face.

    Quote Originally Posted by Freddie View Post
    One of the things I've learned from supporting HotkeyNet for four years is that it doesn't occur to people that the way to write complex scripts is to start with something simple. After the simple thing is working, add to it and make it more complex.

    It seems like the most obvious thing in the world, but it just doesn't occur to people. It never ceases to amaze me. They will post 200-line definitions with embedded templates and includes and say, "I can't figure out what's wrong. Help!"

    Well of course they can't figure out. The definition is too complicated. I can't figure it out either.
    I know exactly what you mean! That's why I used such a simple example. It's much easier to fix the problem at hand if you don't have pages of code to sort through.

    Anyway, as for the problem, it's gone now. Since I learned that I could load a script on the slave client all of my problems have disappeared. I can't believe that after looking through pages and pages of Google results for HotKeyNet, FTL, etc. that I never once seen anything stating to put a script on the slave client. It might have been stated and I just missed it...

    Here's the revised example script and the slave client script I used to test (just in case this helps someone else):

    Master Client:
    Code:
    <Label w1 Local SendWinM WoW1>
    <Label w2 192.168.0.109 SendWinM WoW2>
    <Label w3 192.168.0.109 SendWinM WoW3>
    <Label w4 192.168.0.109 SendWinM WoW4>
    <Label w5 192.168.0.109 SendWinM WoW5>
    
    
    <Hotkey ScrollLockOn Alt Ctrl L>
        <SendPC Local>
        <Run "D:\Program Files\World of Warcraft\WoW.exe">
        <RenameWin World WoW1>
        <wait 10000>
        <SendWinM WoW1>
            <text "Account">
            <wait 500>
            <key Tab>
            <wait 500>
            <text "Pass">
            <wait 100>
            <key Enter>
    
        <SendPC 192.168.0.109>
        <Run "D:\Program Files\World of Warcraft\WoW.exe">
        <RenameWin World WoW2>
        <wait 10000>
        <SendWinM WoW2>
            <SetWinPos 0 0>
            <SetWinSize 704 440>
            <RemoveWinFrame>
            <text "Account">
            <wait 500>
            <key Tab>
            <wait 500>
            <text "Pass">
            <wait 100>
            <key Enter>
    
        <SendPC 192.168.0.109>
        <Run "D:\Program Files\World of Warcraft\WoW.exe">
        <RenameWin World WoW3>
        <wait 10000>
        <SendWinM WoW3>
            <SetWinPos 576 0>
            <SetWinSize 704 440>
            <RemoveWinFrame>
            <text "Account">
            <wait 500>
            <key Tab>
            <wait 500>
            <text "Pass">
            <wait 100>
            <key Enter>
    
        <SendPC 192.168.0.109>
        <Run "D:\Program Files\World of Warcraft\WoW.exe">
        <RenameWin World WoW4>
        <wait 10000>
        <SendWinM WoW4>
            <SetWinPos 0 360>
            <SetWinSize 704 440>
            <RemoveWinFrame>
            <text "Account">
            <wait 500>
            <key Tab>
            <wait 500>
            <text "Pass">
            <wait 100>
            <key Enter>
    
        <SendPC 192.168.0.109>
        <Run "D:\Program Files\World of Warcraft\WoW.exe">
        <RenameWin World WoW5>
        <wait 10000>
        <SendWinM WoW5>
            <SetWinPos 576 360>
            <SetWinSize 704 440>
            <RemoveWinFrame>
            <text "Account">
            <wait 500>
            <key Tab>
            <wait 500>
            <text "Pass">
            <wait 100>
            <key Enter>
    
    
    <Hotkey Numpad1>
        <SendLabel w2, w3, w4, w5>
            <Key Numpad1>
    Slave Client:
    Code:
    <Label w1 192.168.0.110 SendWinM WoW1>
    <Label w2 Local SendWinM WoW2>
    <Label w3 Local SendWinM WoW3>
    <Label w4 Local SendWinM WoW4>
    <Label w5 Local SendWinM WoW5>
    
    
    <Hotkey Numpad1>
        <If ActiveWinIs WoW2>
            <SendLabel w1, w3, w4, w5>
                <Key Numpad2>
        <Else If ActiveWinIs WoW3>
            <SendLabel w1, w2, w4, w5>
                <Key Numpad3>
        <Else If ActiveWinIs WoW4>
            <SendLabel w1, w2, w3, w5>
                <Key Numpad4>
        <Else If ActiveWinIs WoW5>
            <SendLabel w1, w2, w3, w4>
                <Key Numpad5>
    As you can see I removed the "IF" in the master script because it only has one window and is therefore always active when the master system has focus. It's still active when the slave has focus too, but then the slave client script supercedes the master client script.

    Thanks again for your help! I was getting fed up with searching, which is why I made a thread. It takes a lot of agony to get me to ask for help. I'm a big believer in Google, hehe. Now I can get back to the fun stuff.
    Last edited by Nomahd : 02-03-2011 at 05:59 PM Reason: Oops, had an error in my code from changing stuff

Posting Rules

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