16 replies to this topic

[Tom]

my macros all work fine but F10 is wierd when i press it, it highlight character options instead of working like the normal Fnumbers any way to fix this?

[Sneaky]

mine does the same

[jurian]

basic windows settings nothing you can do about it.

f10 = menu in all programs

[Squee]

Is there no way that you can change that settings in Windows?

[jurian]

never found it sorry :S

what i do is press it twice. like /cast rapid fire/pandilex

first f10 will shoot and select the menu. if you press f10 again you will deselect it and can continue moving or using other macros.

also hitting it and then clicking someone will deselect the menu and allow you to continue doing stuff (best is to click the input box thingy so you can type in it right away, if you cick somewhere else you have to click the input bar before you can type in it again )

[Prophet]

Solution: Don't use windows

[Crane]

It is possible to 'trap' the keystrokes and prevent them from activating the menu by intercepting the Windows Messages, but I'm not sure if you can do that in Visual Basic.

[jurian]

lol i dunno either but that would mean jlh has to do some more programming. basicly i dun think there is an easy way for the players to do it

[Prophet]

It can be done in Vb but not worth the time or effort for the amount of stuff that would be required.

[two]

can't you just make it so nightmist sends the signal twice for everytime the button is pushed?

[jurian]

can't you just make it so nightmist sends the signal twice for everytime the button is pushed?

that's actually rather smart. but probably even ebtter would be that after f10 is pused and the signal is sent it selects the input bar again. because when you sent the signal twice it will just unselect the menu and you would still ahve to click the input bar before you can type again.

[Wafer]

can't you just make it so nightmist sends the signal twice for everytime the button is pushed?

that's actually rather smart. but probably even ebtter would be that after f10 is pused and the signal is sent it selects the input bar again. because when you sent the signal twice it will just unselect the menu and you would still ahve to click the input bar before you can type again.

/nod at both Jurian and Two.

Both quite nifty ideas.

In the mean time how I get around it is, as I play with my left hand over alt+tab, i just press alt to deselect menu (cursor stays in input bar).

That and try not to macro things to f10 lol

[jurian]

That and try not to macro things to f10 lol

i think they thought of that allready

[sayadin]

i have the solution to all of your promblems...... don't use F10

[jurian]

read two posts above yours? last line? or read the quote in my post? basicly we are screwed up unless jlh wants to do soemthing about it. *glares at jlh*

[Tom]

can't you just make it so nightmist sends the signal twice for everytime the button is pushed?

fairly sound idea, wonder what jlh will say

[jurian]

my idea should work better i think but jlh is the expert i think he should be able to do something