WheelEvent

Remarks

Its own event rather than a PointerAction, because it carries a quantity the others do not and because the elements that want it are not the elements that want presses. A scroll view listens for this and for nothing else.

⚠ The deltas are in device-independent pixels, already resolved. A wheel notch is not a pixel and every platform disagrees about how many it is worth; that conversion belongs to the backend, which knows what device produced the event and what the user's system settings say. A UI framework that multiplied notches by a constant of its own would scroll at a different speed from every other application on the machine.

Fields and properties (7)

• public int PointerId

  Which pointer.

• public float X

  Where the pointer is, in document space.

• public float Y

  Ditto.

• public float DeltaX

  How far to scroll horizontally, positive meaning towards the content's end.

• public float DeltaY

  Ditto, vertically.

• public ModifierKeys Modifiers

  What was held on the keyboard at the time.

• public TimeSpan Timestamp

  When, on the same clock as the rest.

Used by (16)

• AdvancedFixtureVixen.Ui.Controls.Advanced.Tests
• ControlFixtureVixen.Ui.Controls.Tests
• CurveEditorVixen.Ui.Controls.Advanced
• CurveEditorTestsVixen.Ui.Controls.Advanced.Tests
• InteractionTestsVixen.Ui.Testing.Tests
• NodeCanvasVixen.Ui.Controls.Advanced
• NodeCanvasTestsVixen.Ui.Controls.Advanced.Tests
• PlatformInputVixen.Platform.Ui
• ScrollViewVixen.Ui.Controls
• SurfaceTestsVixen.Ui.Controls.Tests
• TimelineVixen.Ui.Controls.Advanced
• TimelineTestsVixen.Ui.Controls.Advanced.Tests
• UiDocumentVixen.Ui
• UiTestVixen.Ui.Testing
• ViewportVixen.Ui.Controls.Advanced
• NodeGraphViewVixen.Editor.NodeGraph