Hide

SftTree/OCX 7.5 - ActiveX Tree Control

Display
Print

NoSelection Property, SftTree Object

Defines whether the selection changes when the caret location changes.

Deprecated - Provided for compatibility with earlier versions only - Use Items.SelectionArea instead

Syntax

Get

VB.NETBoolean = object.NoSelection As Boolean
VBBoolean = object.NoSelection As Boolean
C#.NETbool Boolean = object.NoSelection;
VC++VARIANT_BOOL Boolean = object->NoSelection;
VARIANT_BOOL Boolean = object->GetNoSelection();
CHRESULT object->get_NoSelection(VARIANT_BOOL* Boolean);

Put

VB.NETobject.NoSelection = Boolean As Boolean
VBobject.NoSelection = Boolean As Boolean
C#.NETbool object.NoSelection = Boolean;
VC++VARIANT_BOOL object->NoSelection = Boolean;
void object->PutNoSelection(VARIANT_BOOL Boolean);
CHRESULT object->put_NoSelection(VARIANT_BOOL Boolean);

object

A SftTree object.

Boolean

Defines whether the selection changes when the caret location changes.

BooleanDescription
TrueThe selection doesn't change when the caret location changes.
FalseThe selection changes when the caret location changes.

Comments

Deprecated - Provided for compatibility with earlier versions only - Use Items.SelectionArea instead

The NoSelection property defines whether the selection changes when the caret location changes.

If the NoSelection property is set to True, the selection does not automatically follow the caret location when the user clicks outside of a cell. If the CONTROL key is used with a directional key (such as an arrow key), the caret location changes, but the current selection remains. This allows a user to click on an expand/collapse button without changing the currently selected item(s).

In a multiple selection tree control, the selection never follows the caret location when the user clicks outside of a cell, regardless of the setting of this property.

See Also SftTree Object | Object Hierarchy


Last Updated 08/13/2020 - (email)
© 2024 Softel vdm, Inc.


Spring Break!

Our offices will be closed this week (March 18 through March 22).

We'll be back March 24 to address any pending sales and support issues.