disableUserInput – Talk
No edit summary |
Lou Montana (talk | contribs) m (Text replacement - "Killzone Kid" to "Killzone_Kid") |
||
| (2 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
==Grumble== | |||
I really wish this command was never used! Please, mission makers, always allow me to escape out. I may wish to join another server or.. A lot of people like to use this command to "punish" team killers by not allowing them to do anything for 5 min. or whatever... the only way to escape this is to ALT-F4 and restart game. Very very annoying! --[[User:Doolittle|Doolittle]] 19:16, 21 June 2007 (CEST) | I really wish this command was never used! Please, mission makers, always allow me to escape out. I may wish to join another server or.. A lot of people like to use this command to "punish" team killers by not allowing them to do anything for 5 min. or whatever... the only way to escape this is to ALT-F4 and restart game. Very very annoying! --[[User:Doolittle|Doolittle]] 19:16, 21 June 2007 (CEST) | ||
== About user input getting stuck == | |||
[[User:Killzone_Kid|Killzone_Kid]]'s note suggests that disabling user input should only be done when no user input is current. I'm new to the platform but expect that user controller actions can be read, so it should be possible to ask (pseudo code) '''if (user is not pressing any keys or moving their mouse) then { disable their input; };''' or even perhaps emulate a lack of input prior to diabling to avoid running into the unexpected behaviour (bug)? [[User:Fred Gandt|Fred Gandt]] ([[User talk:Fred Gandt|talk]]) 04:15, 17 March 2014 (CET) | |||
Latest revision as of 13:48, 12 March 2024
Grumble
I really wish this command was never used! Please, mission makers, always allow me to escape out. I may wish to join another server or.. A lot of people like to use this command to "punish" team killers by not allowing them to do anything for 5 min. or whatever... the only way to escape this is to ALT-F4 and restart game. Very very annoying! --Doolittle 19:16, 21 June 2007 (CEST)
About user input getting stuck
Killzone_Kid's note suggests that disabling user input should only be done when no user input is current. I'm new to the platform but expect that user controller actions can be read, so it should be possible to ask (pseudo code) if (user is not pressing any keys or moving their mouse) then { disable their input; }; or even perhaps emulate a lack of input prior to diabling to avoid running into the unexpected behaviour (bug)? Fred Gandt (talk) 04:15, 17 March 2014 (CET)