VirtualBox

Changeset 20828 in vbox for trunk/src/VBox/Main


Ignore:
Timestamp:
Jun 23, 2009 12:58:29 PM (16 years ago)
Author:
vboxsync
Message:

SDK: documentation updates

File:
1 edited

Legend:

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

    r20814 r20828  
    29992999      </param>
    30003000    </method>
    3001    
     3001
    30023002  </interface>
    30033003
     
    55795579     >
    55805580
     5581    <desc>
     5582        This interface is used by a client of the Main API that need to
     5583        be notified of events. For example, a graphical user interface
     5584        can use this to learn about machine state changes so they can
     5585        update the list of virtual machines without having to rely
     5586        on polling.
     5587
     5588        Whenever relevant events occur in VirtualBox, the callbacks in
     5589        objects of this interface are called. In order for this to be
     5590        useful, a client needs to create its own subclass that implements
     5591        this interface in which the methods for the relevant callbacks
     5592        are overridden. An instance of this subclass interface can then
     5593        be passed to <link to="IConsole::registerCallback" />.
     5594    </desc>
     5595
    55815596    <method name="onMousePointerShapeChange">
    55825597      <desc>
     
    84178432      interface such as:
    84188433      <ul>
    8419         <li>IHardDisk (virtual hard disks)</li>
    8420         <li>IDVDImage (standard CD/DVD ISO image files)</li>
    8421         <li>IFloppyImage (raw floppy image files)</li>
     8434        <li><link to="IHardDisk" /> (virtual hard disks)</li>
     8435        <li><link to="IDVDImage" /> (standard CD/DVD ISO image files)</li>
     8436        <li><link to="IFloppyImage" /> (raw floppy image files)</li>
    84228437      </ul>
    84238438
     
    86908705
    86918706        This method sets the media state to <link
    8692         to="MediaState_LockedRead"/> on success. The state prior to
    8693         this call must be <link to="MediaState_Created"/>, <link
    8694         to="MediaState_Inaccessible"/> or <link
    8695         to="MediaState_LockedRead"/>. As you can see, inaccessible
    8696         media can be locked too. This is not an error; this method
    8697         performs a logical lock that prevents modifications of this
    8698         media through the VirtualBox API, not a physical lock of the
    8699         underlying storage unit.
     8707        to="MediaState_LockedRead" /> on success. The state prior to
     8708        this call must be <link to="MediaState_Created" />,
     8709        <link to="MediaState_Inaccessible" /> or
     8710        <link to="MediaState_LockedRead" />.
     8711        As you can see, inaccessible media can be locked too. This is
     8712        not an error; this method performs a logical lock that prevents
     8713        modifications of this media through the VirtualBox API, not a
     8714        physical lock of the underlying storage unit.
    87008715
    87018716        This method returns the current state of the medium
     
    87618776        to="#unlockWrite"/> call before the next lockWrite call.
    87628777
    8763         This method sets the media state to <link
    8764         to="MediaState_LockedWrite"/> on success. The state prior to
    8765         this call must be <link to="MediaState_Created"/> or <link
    8766         to="MediaState_Inaccessible"/>. As you can see, inaccessible
     8778        This method sets the media state to <link to="MediaState_LockedWrite" />
     8779        on success. The state prior to this call must be <link to="MediaState_Created"/>
     8780        or <link to="MediaState_Inaccessible"/>. As you can see, inaccessible
    87678781        media can be locked too. This is not an error; this method
    87688782        performs a logical lock preventing modifications of this
     
    1071410728      </param>
    1071510729    </method>
    10716    
     10730
    1071710731    <method name="processVHWACommand">
    1071810732      <desc>
     
    1072010734        The commands used for 2D video acceleration (DDraw surface creation/destroying, blitting, scaling, color covnersion, overlaying, etc.)
    1072110735        are posted from quest to the host to be processed by the host hardware.
    10722        
     10736
    1072310737        <note>
    1072410738          The address of the provided command must be in the process space of
     
    1072610740        </note>
    1072710741      </desc>
    10728    
     10742
    1072910743      <param name="command" type="octet" mod="ptr" dir="in">
    1073010744        <desc>Pointer to VBOXVHWACMD containing the command to execute.</desc>
     
    1097110985        Signals that the Video HW Acceleration command has completed.
    1097210986      </desc>
    10973  
     10987
    1097410988      <param name="command" type="octet" mod="ptr" dir="in">
    1097510989        <desc>Pointer to VBOXVHWACMD containing the completed command.</desc>
     
    1309713111      stores performance metrics data.
    1309813112
    13099       Performance metrics are associated with objects like IHost and
     13113      Performance metrics are associated with objects of interfaces like IHost and
    1310013114      IMachine. Each object has a distinct set of performance metrics.
    1310113115      The set can be obtained with <link to="IPerformanceCollector::getMetrics"/>.
    1310213116
    13103       Metric data are collected at the specified intervals and are retained
    13104       internally. The interval and the number of samples retained can be set
     13117      Metric data is collected at the specified intervals and is retained
     13118      internally. The interval and the number of retained samples can be set
    1310513119      with <link to="IPerformanceCollector::setupMetrics" />.
    1310613120
    13107       Metrics are organized hierarchically, each level separated by slash (/).
    13108       General scheme for metric name is
    13109       "Category/Metric[/SubMetric][:aggregation]". For example CPU/Load/User:avg
    13110       metric name stands for: CPU category, Load metric, User submetric, average
    13111       aggregate. An aggregate function is computed over all retained data. Valid
    13112       aggregate functions are:
    13113 
    13114       <ul>
    13115       <li>avg -- average</li>
    13116       <li>min -- minimum</li>
    13117       <li>max -- maximum</li>
    13118       </ul>
    13119 
    13120       "Category/Metric" together form base metric name. A base metric is the
     13121      Metrics are organized hierarchically, with each level separated by a
     13122      slash (/) character. Generally, the scheme for metric names is like this:
     13123
     13124      <tt>Category/Metric[/SubMetric][:aggregation]</tt>
     13125
     13126      "Category/Metric" together form the base metric name. A base metric is the
    1312113127      smallest unit for which a sampling interval and the number of retained
    1312213128      samples can be set. Only base metrics can be enabled and disabled. All
    1312313129      sub-metrics are collected when their base metric is collected.
    1312413130      Collected values for any set of sub-metrics can be queried with
    13125       <link to="IPerformanceCollector::queryMetricsData" />. When setting up
     13131      <link to="IPerformanceCollector::queryMetricsData" />.
     13132
     13133      For example "CPU/Load/User:avg"
     13134      metric name stands for the "CPU" category, "Load" metric, "User" submetric,
     13135      "average" aggregate. An aggregate function is computed over all retained
     13136      data. Valid aggregate functions are:
     13137
     13138      <ul>
     13139          <li>avg -- average</li>
     13140          <li>min -- minimum</li>
     13141          <li>max -- maximum</li>
     13142      </ul>
     13143
     13144      When setting up
    1312613145      metric parameters, querying metric data, enabling or disabling metrics
    1312713146      wildcards can be used in metric names to specify a subset of metrics. For
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