Back to product page
- Introduction
- License agreement
- Getting Started
- Enumerations
- Objects
- wodTelnetDLX
- Methods
- Properties
- Authentication
- AutoSize
- BackColor
- BackLog
- BindIP
- BindPort
- Blocking
- BorderVisible
- Certificate
- CharEncoding
- Column
- Columns
- ColWidth
- Command
- ContextMenu
- CursorHeight
- DataOut
- DataReady
- Enabled
- ErrorText
- ExitSignal
- ExitStatus
- Font
- ForeColor
- HandleSysKeys
- Hostname
- hWnd
- KeepAlives
- Language
- LastError
- LocalCertBag
- Login
- MousePointer
- MouseWheel
- MyHostname
- MyIP
- Notification
- Password
- Picture
- Port
- Prompt
- Protocol
- ProxyHostname
- ProxyLogin
- ProxyPassword
- ProxyPort
- ProxyType
- RecordMode
- RemoteIdentification
- Row
- RowHeight
- Rows
- ScrollBars
- ScrollX
- ScrollY
- SecureMethod
- SelectedText
- ShowCursor
- Socket
- SpecialKeyFocus
- State
- StateText
- StripANSI
- StripColors
- TabStop
- TelnetOption
- TerminalEmulation
- TerminalType
- Text
- Timeout
- TranslateSpecial
- UseIPv6
- Version
- Events
- IwodTelnetNotify
- wodTelnetDLX
- How to get support?
- Technical information
- Fast notifications interface
- Error list
HandleSysKeys property
Determines whether a control is handling system keys (such as ALT+F4).
Type
BooleanSyntax
- Basic
object.HandleSysKeys [= value]
The HandleSysKeys(object) syntax has these parts:
The HandleSysKeys(object) syntax has these parts:
object | An expression evaluating to an object of type wodTelnetDLX |
Remarks
This property is only available in OCX (GUI) version of the component.HandleSysKeys property determines if wodTelnetDLX will capture system keys, instead of passing them to the application. This allows you to capture keys reserved by the application, such as F10, to be processed by your own code.
However, this property defaults to False, since when set to True it even disables ALT+F4 and you need to handle it by yourself.