GuiGetInputMode: Difference between revisions

From Multi Theft Auto: Wiki
Jump to navigation Jump to search
(Created page with "{{Client function}} __NOTOC__ This function returns the current input mode as set by guiSetInputMode. ==Syntax== <syntaxhighlight lang="lua"> string guiGetInputMode ( ) </syntaxhighlight> ===Return...")
 
No edit summary
Line 2: Line 2:
__NOTOC__
__NOTOC__
This function returns the current input mode as set by [[guiSetInputMode]].
This function returns the current input mode as set by [[guiSetInputMode]].
Default mode is ''"allow_binds"''.


==Syntax==  
==Syntax==  

Revision as of 21:10, 18 November 2010

This function returns the current input mode as set by guiSetInputMode. Default mode is "allow_binds".

Syntax

string guiGetInputMode ( )

Returns

Returns a string defining the current input mode, potential values are:

    • "allow_binds": binds are enabled, hence using a key such as t in an editbox will still activate the chatbox
    • "no_binds": binds are disabled, hence using a key such as t in an editbox will still activate the chatbox
    • "no_binds_when_editing": binds are always enabled except when an editable editbox or memo has input focus

Example

Click to collapse [-]
Client
addCommandHandler( "checkmode", 
function ()
    outputChatBox( string.format( "The current input mode is: '%s'", guiGetInputMode () ) )
end )

Note

This function, introduced in 1.1, is not a replacement of guiGetInputEnabled, indeed for the mode "no_binds_when_editing" the actual state of binds depends on the currently focused GUI widget. However:

  • when guiGetInputMode ( ) returns "allow_binds" you can be sure that guiGetInputEnabled () will return false
  • when guiGetInputMode ( ) returns "no_binds" you can be sure that guiGetInputEnabled () will return true

See Also

General functions

Browsers

Buttons

Checkboxes

Comboboxes

Edit Boxes

Gridlists

Memos

Progressbars

Radio Buttons

Scrollbars

Scrollpanes

Static Images

Tab Panels

Tabs

Text Labels

Windows