'Declaration Public Shared ReadOnly ScrollToNextColumnVisual As Object
'Usage Dim value As Object value = SpreadActions.ScrollToNextColumnVisual
public static readonly object ScrollToNextColumnVisual
'Declaration Public Shared ReadOnly ScrollToNextColumnVisual As Object
'Usage Dim value As Object value = SpreadActions.ScrollToNextColumnVisual
public static readonly object ScrollToNextColumnVisual
FarPoint.Win.Spread.InputMap im;
im = fpSpread1.GetInputMap(FarPoint.Win.Spread.InputMapMode.WhenFocused);
im.Put(new FarPoint.Win.Spread.Keystroke(Keys.P, Keys.None), FarPoint.Win.Spread.SpreadActions.ScrollToNextColumnVisual);Dim im As FarPoint.Win.Spread.InputMap im = fpSpread1.GetInputMap(FarPoint.Win.Spread.InputMapMode.WhenFocused) im.Put(New FarPoint.Win.Spread.Keystroke(Keys.P, Keys.None), FarPoint.Win.Spread.SpreadActions.ScrollToNextColumnVisual)
This action scrolls the display to the next column to the right by visual layout in the sheet. This action is similar to the ScrollToNextColumn action. The difference is in the meaning of Next. Instead of defining Next based on cell coordinates (that is, NextColumn is ActiveColumn + 1), this action defines Next based on the left to right visual layout of the columns on the screen (that is, PreviousColumn is column that is visually left of ActiveColumn and NextColumn is column that is visually right of ActiveColumn). With the new actions and bindings, the left key will always move left and the right key will always move right regardless of the control's RightToLeft property setting. The suffix "Visual" (as in MoveToNextColumnVisual) indicates that the action is using a visual ordering (for example, next column is defined as the column to the right) rather than a logic ordering (for example, next column index is defined as current column index + 1). The Visual suffix on the names of the actions added in version 3.0 indicates that the definition of Next is based on the left-to-right visual layout of the columns.
You can use this action along with a custom key combination by defining your own input or action map. For more information about maps, see Managing Keyboard Interactions.