A minor suggestion for the voting keys/numbers

**Imisnew2** · 09-07-10, 12:21 PM

Hmm...
While I like the idea, it doesn't remove the problem:
Needing to be able to swap weapons while a vote is open.

**Ewok** · 09-07-10, 08:41 PM

Imis the code is in menu.py

What you probably need to do is introduce the idea of a numbering offset property with each menu, so that when we generate the menu, we start numbering from the offset (and taking into account that the offset means less choices per menu).

And bunni, redirecting client bindings like you're suggesting would require a client side hook. At best we can send console commands to a client (and I thought there was a client side setting that allows a client to block that)

**Imisnew2** · 09-07-10, 10:54 PM

I'll look into it later. Maybe Sunday. Might be earlier.

**Bunni** · 09-08-10, 11:53 AM

Originally Posted by Ewok

Imis the code is in menu.py

What you probably need to do is introduce the idea of a numbering offset property with each menu, so that when we generate the menu, we start numbering from the offset (and taking into account that the offset means less choices per menu).

And bunni, redirecting client bindings like you're suggesting would require a client side hook. At best we can send console commands to a client (and I thought there was a client side setting that allows a client to block that)

ya so we request that they allow it for our server, have a serverside client preferences that reflects which method a user wants to use to vote (number keys [def], or keypad), then we can use bindlist...

actually a thought, can the menu be set to listen to any specific command correlating to a menu item option?

hell, maybe just ahve a new chat command "vote [option], ex "vote 3", as a client pref (type to vote (which is filtered from chat like the rest of the chat commands, OR the default invslot keyboard voting method)?

**Imisnew2** · 09-08-10, 02:06 PM

It makes sense... but what we cannot do is change the voting from the menu to ONLY the keypad. This does not fix the issue of the voting "overwriting" swapping weapons... That is until I can test changing the numbers.

**Bunni** · 09-08-10, 05:17 PM

well the point i was leading to was making our own client side commands to control the menus, rather than the invslot ones.

But i do like my idea of chat voting, and having a client preferences for one or the other.

**~~insanegammer109~~** · 09-08-10, 11:45 PM

Originally Posted by Bunni

well the point i was leading to was making our own client side commands to control the menus, rather than the invslot ones.

But i do like my idea of chat voting, and having a client preferences for one or the other.

LS would need to support client profiles first so it can remember options you have set.

**Ewok** · 09-08-10, 11:57 PM

Accepting random console commands for vote options isn't a problem (just takes work), the issue is that when you pop up the menu, the game engine handles the input control and expeccts "slot0" - "slot9" to be used. If you don't hit one of them, the engine keeps the menu up there waiting for you to hit one (some games will kill the menu automatically if you don't hit one within 4 seconds)