/usr/share/doc/python-pytango-doc/html/_sources/client_api/miscellaneous.txt is in python-pytango-doc 8.1.5-1.
This file is owned by root:root, with mode 0o644.
The actual contents of the file can be viewed below.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 | .. currentmodule:: PyTango
API util
--------
.. autoclass:: ApiUtil
:members:
Information classes
-------------------
See also `Event configuration information`_
Attribute
~~~~~~~~~
.. autoclass:: AttributeAlarmInfo
:members:
.. autoclass:: AttributeDimension
:members:
.. autoclass:: AttributeInfo
:members:
.. autoclass:: AttributeInfoEx
:members:
see also :class:`AttributeInfo`
.. autoclass:: DeviceAttributeConfig
:members:
Command
~~~~~~~
.. autoclass:: DevCommandInfo
:members:
.. autoclass:: CommandInfo
:members:
Other
~~~~~
.. autoclass:: DeviceInfo
:members:
.. autoclass:: LockerInfo
:members:
.. autoclass:: PollDevice
:members:
Storage classes
---------------
Attribute: DeviceAttribute
~~~~~~~~~~~~~~~~~~~~~~~~~~
.. autoclass:: DeviceAttribute
:members:
Command: DeviceData
~~~~~~~~~~~~~~~~~~~
Device data is the type used internally by Tango to deal with command parameters
and return values. You don't usually need to deal with it, as command_inout
will automatically convert the parameters from any other type and the result
value to another type.
You can still use them, using command_inout_raw to get the result in a DeviceData.
You also may deal with it when reading command history.
.. autoclass:: DeviceData
:members:
Callback related classes
------------------------
If you subscribe a callback in a DeviceProxy, it will be run with a parameter.
This parameter depends will be of one of the following classes depending on
the callback type.
.. autoclass:: AttrReadEvent
:members:
.. autoclass:: AttrWrittenEvent
:members:
.. autoclass:: CmdDoneEvent
:members:
Event related classes
---------------------
Event configuration information
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
.. autoclass:: AttributeEventInfo
:members:
.. autoclass:: ArchiveEventInfo
:members:
.. autoclass:: ChangeEventInfo
:members:
.. autoclass:: PeriodicEventInfo
:members:
Event arrived structures
~~~~~~~~~~~~~~~~~~~~~~~~
.. autoclass:: EventData
:members:
.. autoclass:: AttrConfEventData
:members:
.. autoclass:: DataReadyEventData
:members:
History classes
---------------
.. autoclass:: DeviceAttributeHistory
:show-inheritance:
:members:
See :class:`DeviceAttribute`.
.. autoclass:: DeviceDataHistory
:show-inheritance:
:members:
See :class:`DeviceData`.
|