VirtualBox

Changeset 47174 in vbox for trunk/src/VBox/Main/idl


Ignore:
Timestamp:
Jul 16, 2013 3:27:24 AM (12 years ago)
Author:
vboxsync
svn:sync-xref-src-repo-rev:
87278
Message:

Devices/Input: most of the Main plumbing for guest multi-touch.

File:
1 edited

Legend:

Unmodified
Added
Removed
  • trunk/src/VBox/Main/idl/VirtualBox.xidl

    r47124 r47174  
    1429714297    </attribute>
    1429814298
     14299    <attribute name="multiTouchSupported" type="boolean" readonly="yes">
     14300      <desc>
     14301        Whether the guest OS supports multi-touch event reporting.
     14302        <note>
     14303          You can use the <link to="IMouseCapabilityChangedEvent"/>
     14304          event to be instantly informed about changes of this attribute
     14305          during virtual machine execution.
     14306        </note>
     14307        <see><link to="#putMouseEvent"/></see>
     14308      </desc>
     14309    </attribute>
     14310
    1429914311    <attribute name="needsHostCursor" type="boolean" readonly="yes">
    1430014312      <desc>
     
    2021420226  </interface>
    2021520227
     20228  <enum
     20229    name="GuestMouseEventMode"
     20230    uuid="ef172985-7e36-4297-95be-e46396968d66"
     20231    >
     20232
     20233    <desc>
     20234      The mode (relative, absolute, multi-touch) of a pointer event.
     20235      TODO: a clear pattern seems to be emerging that we should usually have
     20236      multiple input devices active for different types of reporting, so we
     20237      should really have different event types for relative (including wheel),
     20238      absolute (not including wheel) and multi-touch events.
     20239    </desc>
     20240
     20241    <const name="Relative" value="0">
     20242      <desc>
     20243        Relative event.
     20244      </desc>
     20245    </const>
     20246
     20247    <const name="Absolute" value="1">
     20248      <desc>
     20249        Absolute event.
     20250      </desc>
     20251    </const>
     20252
     20253    <const name="MultiTouch" value="2">
     20254      <desc>
     20255        Multi-touch event.
     20256      </desc>
     20257    </const>
     20258  </enum>
     20259
    2021620260  <interface
    2021720261    name="IGuestMouseEvent" extends="IReusableEvent"
     
    2022320267    </desc>
    2022420268
    20225     <attribute name="absolute" type="boolean" readonly="yes">
    20226       <desc>
    20227         If this event is relative or absolute.
     20269    <attribute name="mode" type="GuestMouseEventMode" readonly="yes">
     20270      <desc>
     20271        If this event is relative, absolute or multi-touch.
    2022820272      </desc>
    2022920273    </attribute>
     
    2025320297    </attribute>
    2025420298
     20299    <attribute name="contact" type="long" readonly="yes">
     20300      <desc>
     20301        The multi-touch contact identifier.  This remains valid as long as a
     20302        touch is in progress and can and should be re-used after a touch has
     20303        terminated (see @a buttons).
     20304      </desc>
     20305    </attribute>
     20306
    2025520307    <attribute name="buttons" type="long" readonly="yes">
    2025620308      <desc>
    20257         Button state bitmask.
     20309        Button state bitmask.  Multi-touch events should have the first bit set
     20310        as long as the touch is in progress and terminate with an event with no
     20311        bits set.
    2025820312      </desc>
    2025920313    </attribute>
Note: See TracChangeset for help on using the changeset viewer.

© 2024 Oracle Support Privacy / Do Not Sell My Info Terms of Use Trademark Policy Automated Access Etiquette