or [HotKeyNet] functionality

[wolpak]

Ok, off to lunch, I expect this problem resolved by the time I return. Not often I can take a day off and was actually hoping to play...rofl...

[wolpak]

Wonder how that will effect gameplay with no dragging. Guess a lot since I wouldn't be able to drag icons or spells onto stuff and whatnot.

Oh yeah, I couldn't stand that. That's why I would use RButton for this. But like I said, if you want to use this, I'll finish it up so it drags. I should say, I'll try to do that ... it may not be so easy. I generally work on things that people nag me about or at least tell me they're using, and nobody has ever complained about this, so it's been on the back burner.

Ok, here are two screenshots.

Great. Does this mean the coordinates are working okay?

Ok, that makes sense, will use the right button, but after I finally get it working. Screenshots show how the coords are all off. How one icon on the right runs the command for the icon on the left. Though, in theory, it is working and I am happy about that. However, I'd like it to work correctly.

[Freddie]

Ok, I couldn't print screen the coords since it goes to the print screen info instead. Either way, I promise those are the win coords of that button. The other button with the seal ends up sending the command over and it is nowhere near those coords.

Have a great lunch. I don't understand this though -- there's a problem with one of the buttons? If you paste the script, and explain where you're clicking, and tell me what messages the program displays, I can do something about it.

[wolpak]

Oh and my guys are really bored waiting for me, just sitting around shooting the shtuff...

[Freddie]

I'd like it to work correctly.

Of course, me too! Help me understand what's wrong and i'll post a new build with a fix later today.

By the way, you may be the first person who ever tested this. I can't remember if I received any other reports on this feature.

[wolpak]

Ok, I couldn't print screen the coords since it goes to the print screen info instead. Either way, I promise those are the win coords of that button. The other button with the seal ends up sending the command over and it is nowhere near those coords.

Have a great lunch. I don't understand this though -- there's a problem with one of the buttons? If you paste the script, and explain where you're clicking, and tell me what messages the program displays, I can do something about it.

I captured where I was clicking in the screenshot. I left the HKN and the script open enough to see. Sorry, forgot you don't read minds. Anyway, here's the script cut...




<Hotkey LButton>
<If MouseIsOverWindowRect Wow1 635 471 666 444>
<SendLabel shaman>
<Key ctrl numpad3>
<Else>
<SendFocusWin>
<ClickMouse NoMove %Trigger%>

However, in the screenshot, that is the location of the axe that is labeled rockbiter. When I click that, nada. However, when I click the action bar on the right with the seal, instead of triggering the seal, it puts rockbiter on the shaman. Teh seal's coords are 1167 479 which is nowehere near what I have in the mouseoverwindowrect. I then tried this script...

<Hotkey LButton>
<If MouseIsOverWindowRect Wow1 335 171 366 144>
<SendLabel shaman>
<Key ctrl numpad3>
<Else>
<SendFocusWin>
<ClickMouse NoMove %Trigger%>

And it would trigger when I clicked the attack icon I have at 688 736. Again, nowhere near the location in the script.

[wolpak]

I'd like it to work correctly.

Of course, me too! Help me understand what's wrong and i'll post a new build with a fix later today.

By the way, you may be the first person who ever tested this. I can't remember if I received any other reports on this feature.

I didn't even know it was a feature. I read much of your wiki and looked through the commands but I never saw mouseoverwinrect in there or how it could function. I am willing to bet that a lot of people would love to send commands to their slaves from their main by clicking on a button on their screen. Kinda like a virtual keyboard.

[Owltoid]

Damn Freddie, you're a freaking saint. Wolpak has been demanding and rude this whole thread, especially with complaining about his guys just sitting around and how it better be resolved by after lunch... you're a better man than I, that's for sure.

[wolpak]

Damn Freddie, you're a freaking saint. Wolpak has been demanding and rude this whole thread, especially with complaining about his guys just sitting around and how it better be resolved by after lunch... you're a better man than I, that's for sure.

I thinks he realizes I was kidding.

[Freddie]

I thinks he realizes I was kidding.

You were? I thought it was really lunch time. <Burp>

All right, I"m going to try your hotkey now. Back in a little while.

Oh, about reading the documentation and not seeing this. It's documented very briefly on the reference page for "If." And it was discussed at great length in HotkeyNet's forum when it was in the planning stages. But other than that, I usually don't advertise this kind of feature until it has been in the program long enough for bug reports to come in and get it debugged. Otherwise people run into a bug and get upset and think the program sucks. A lot of people don't understand what "beta test" means.