Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision		 Previous revision
indigo_2025.1_documentation:schedule_class [2026/02/19 17:43] – [Class Properties] davel17indigo_2025.1_documentation:schedule_class [2026/02/19 21:11] (current) – [Schedule Base Class] davel17
Line 7: Line 7:
 Like other high-level objects in Indigo, there are rules for modifying schedules. For Scripters and Plugin Developers: Like other high-level objects in Indigo, there are rules for modifying schedules. For Scripters and Plugin Developers:
  
-  - To create, duplicate, delete, and send commands to a schedule, use the command namespace as described below +  - To duplicate, delete, and send commands to a schedule, use the command namespace as described below 
-  - To modify an object's definition, get a copy of the schedule, make the necessary changes, then call //''mySchedule.replaceOnServer(newPropsDict)''// +  - To modify an object's definition, get a copy of the schedule, make the necessary changes, then call //''mySchedule.replaceSharedPropsOnServer(newPropsDict)''// (see below).
- +
-For Plugin Developers: +
- +
-  - To update a plugin's props on a schedule, call //''mySchedule.replacePluginPropsOnServer(newPropsDict)''// rather than try to update them on the local schedule +
- +
-Unlike [[device_class|Devices]], you can't call //''create()''// in the the schedule base class command namespace (//''indigo.schedule.*''//). Rather, each subclass has its own //''create()''// method that takes the appropriate arguments for that schedule type.+
  
 ==== Class Properties ==== ==== Class Properties ====
  • /www/perceptive/wiki/data/attic/indigo_2025.1_documentation/schedule_class.1771523021.txt.gz
  • Last modified: 2026/02/19 17:43
  • by davel17