mirror of
https://github.com/tiqi-group/pydase.git
synced 2025-06-11 07:47:12 +02:00
moves state persistence section into docs, restructuring docs
This commit is contained in:
@ -36,7 +36,7 @@ class MyService(pydase.DataService):
|
||||
# ...
|
||||
```
|
||||
|
||||

|
||||

|
||||
|
||||
You can still define synchronous tasks with arguments and call them using a python client. However, decorating them with the `@frontend` decorator will raise a `FunctionDefinitionError`. Defining a task with arguments will raise a `TaskDefinitionError`.
|
||||
I decided against supporting function arguments for functions rendered in the frontend due to the following reasons:
|
||||
@ -83,7 +83,7 @@ if __name__ == "__main__":
|
||||
Server(service).run()
|
||||
```
|
||||
|
||||

|
||||

|
||||
|
||||
**Note** that defining classes within `DataService` classes is not supported (see [this issue](https://github.com/tiqi-group/pydase/issues/16)).
|
||||
|
||||
@ -132,7 +132,7 @@ if __name__ == "__main__":
|
||||
pydase.Server(service_instance).run()
|
||||
```
|
||||
|
||||

|
||||

|
||||
|
||||
#### Customizing Connection Logic
|
||||
|
||||
@ -214,7 +214,7 @@ if __name__ == "__main__":
|
||||
pydase.Server(service).run()
|
||||
```
|
||||
|
||||

|
||||

|
||||
|
||||
### `NumberSlider`
|
||||
|
||||
@ -291,7 +291,7 @@ if __name__ == "__main__":
|
||||
|
||||
In this example, `MySlider` overrides the `min`, `max`, `step_size`, and `value` properties. Users can make any of these properties read-only by omitting the corresponding setter method.
|
||||
|
||||

|
||||

|
||||
|
||||
- Accessing parent class resources in `NumberSlider`
|
||||
|
||||
@ -424,7 +424,7 @@ my_service = StatusExample()
|
||||
my_service.status = MyStatus.FAILED
|
||||
```
|
||||
|
||||

|
||||

|
||||
|
||||
**Note** that each enumeration name and value must be unique.
|
||||
This means that you should use different colour formats when you want to use a colour multiple times.
|
||||
|
Reference in New Issue
Block a user