20,741
edits
Nasal Events: Difference between revisions
Jump to navigation
Jump to search
m
→Summary
m (→Summary) |
m (→Summary) |
||
| Line 13: | Line 13: | ||
* Furthermore, it would make sense to automatically release/restart certain timers depending on their scope/lifetime (aircraft-reset, GUI reset, I/O reset)prefer having some | * Furthermore, it would make sense to automatically release/restart certain timers depending on their scope/lifetime (aircraft-reset, GUI reset, I/O reset)prefer having some | ||
* Basically, timers could be registered with a scope-specific context, so that timers for different purposes would be stored in categories, so that all timers in a group can be safely shut down, and restarted (imagine restarting the GUI, changing the position, resetting the whole sim or changing the active aircraft) - we would ideally want to be able to maintain callbacks for timers/listeners in corresponding groups, so that other callbacks are not affected | * Basically, timers could be registered with a scope-specific context, so that timers for different purposes would be stored in categories, so that all timers in a group can be safely shut down, and restarted (imagine restarting the GUI, changing the position, resetting the whole sim or changing the active aircraft) - we would ideally want to be able to maintain callbacks for timers/listeners in corresponding groups, so that other callbacks are not affected | ||
* The | * more complex scripts (bombable, local weather, aircraft like the concorde) usually end up implementing their own "scheduler" on top of settimer() - this should be recognized, and a generic schedule facility provided that addresses the shortcomings and challenges presented here | ||
* The new maketimer() API could be extended accordingly | |||
== Objective == | == Objective == | ||