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
|
# Group
```{eval-rst}
.. currentmodule:: tango
```
% GroupElement is the base class of Group, but is not the base of
% anything else. So, I don't include it in the documentation but just
% add its functions into Group by using :inherited-members:
## Group class
```{eval-rst}
.. autoclass:: tango.Group
:show-inheritance:
:inherited-members:
:members:
```
## GroupReply classes
Group member functions do not return the same as their DeviceProxy counterparts,
but objects that contain them. This is:
> - *write attribute* family returns tango.GroupReplyList
> - *read attribute* family returns tango.GroupAttrReplyList
> - *command inout* family returns tango.GroupCmdReplyList
The Group\*ReplyList objects are just list-like objects containing
{class}`~tango.GroupReply`, {class}`~tango.GroupAttrReply` and
{class}`~GroupCmdReply` elements that will be described now.
Note also that GroupReply is the base of GroupCmdReply and GroupAttrReply.
```{eval-rst}
.. autoclass:: tango.GroupReply
:members:
```
```{eval-rst}
.. autoclass:: tango.GroupAttrReply
:show-inheritance:
:members:
```
```{eval-rst}
.. autoclass:: GroupCmdReply
:show-inheritance:
:members:
```
|
