The MMDeviceBase type exposes the following members.
This is used from the startup scripts to build the propertylist without using the default propertylist
Runs all device property change requests that have been made since the device was declared busy.
Allows an Object to attempt to free resources and perform other cleanup operations before the Object is reclaimed by garbage collection.(Inherited from Object.)
Returns active property list for this device. Values autoupdate and produce an event to ensure all users have the same value
Gets active information from each single property value for this device. Values autoupdate and produce an event to ensure all users have the same value
Returns all the gory details about the property given in propname
Gets a list of all the property names possible for this device.
Gets the value of the device property directly from Micromanager or whatever is the source
Gets a snapshot of all the device properties and their current values
Serves as a hash function for a particular type.(Inherited from Object.)
Gets the Type of the current instance.(Inherited from Object.)
This builds the device property list. It must be called before the device does anything. Setting clear properties to false allows the device adapter or user to build the property list in several steps. This is useful for devices that have both real micromanager properties as well as virtual properties such as the function generators
If this is a common device, then this will register the device with micromanager and easycore that it is the go-to device
Creates a shallow copy of the current Object.(Inherited from Object.)
Receives notification that the value has been updated
Determines if a device property has been marked as needing to be saved
This runs a CommandState command. This is used to change a property value, or can be a custom command for this device
Sets the value of the device property. All values must be strings as this is the protocol set by micromanager. If the device is busy, then this will wait until the device is ready to accept commands
Connects the default property listing GUI to this device. The properties are automatically loaded into the prop list.
Usually called on shut down to get the device to quit
This should be set when the device should not be interupped such as the stage being in motion, or an expose has started
All devices should be given a name, but it does not have to be unique
Notifications to the GUI on how it should behave. This is very important for those devices that are virtual, (especially scripts.)
Some device properties are not saved from one session to the next This gives a list of those properties that the user defined as needing to be saved