Chronos Plugins 5.9.0
This documentation covers the plugin interfaces definitions and an example implementation.
|
Example task implementations. Since there are lots of things that can be done from a task, the demo was split into many different examples each showing only few facets of what's possible. If you still think this is confusing, please let us know where we could simplify these examples. More...
Classes | |
class | BrewCoffee |
Calls a method of the device class with one if its task parameters. More... | |
class | BrewFrappuccino |
A task working on a complex parameter set. More... | |
class | CoffeeCategory |
Custom category in the method editor for coffee making related tasks. More... | |
class | CoffeeMachineBaseTask |
Base class for our example, just contains some empty default implementations and a check for the right device type. More... | |
class | CoffeeMachineDoesNotWorkProperly |
In contrast to PretendCoffeeMachineIsBroken, this simulates an error that an autosampler could have while it is used by a task. More... | |
class | DumpConfigInfo |
This tasks uses the config helper to access some information about the instrument configuration and just dumps it to the runlog. More... | |
class | FlexibleArguments |
This task demonstrates how to use a custom type descriptor to implement a dynamic list of properties. The number of properties can be changed by setting the PropCount property. More... | |
class | FrappuccinoCompositionEditor |
Provides an editor for the BrewFrappuccino-Task's "Composition" information. More... | |
class | JobInspectionDemo |
Shows how to get information about other tasks in the schedule. More... | |
class | MockDynamicPropsDependingOnDevice |
This task demonstrates how to make the property list depend on the picked autosampler. More... | |
class | MockMethodEditorSnoopingTask |
This task just shows how you can react on the method editor contents and provide context sensitive property standard values. More... | |
class | MockUseMultipleDevicesTask |
For some special cases it can be necessary to have a single task communicate with two different devices. More... | |
class | PretendCoffeeMachineIsBroken |
This task will trigger a timer in our device which will make it complain about an error situation, even if at that time no task is trying to use it. More... | |
class | ShowSomeGreeting |
A task which does not need access to the custom device. More... | |
class | TaskListAttribute |
This attribute uses the task to which it is applied to query for other tasks in the method editor. The list of returned values is just a list of the tasks currently in the method editor. More... | |
class | UseTrain |
Just show that some kind of operation can be done with our "Train" device parts. More... | |
Example task implementations. Since there are lots of things that can be done from a task, the demo was split into many different examples each showing only few facets of what's possible. If you still think this is confusing, please let us know where we could simplify these examples.