Disable OVC during ramping and apply initial scale/angle.
2 unresolved threads
2 unresolved threads
Compare changes
Files
2+ 13
− 0
@@ -162,6 +162,10 @@ class Automation : public ctk::ModuleGroup {
@@ -201,6 +205,8 @@ class Automation : public ctk::ModuleGroup {
@@ -253,6 +259,13 @@ class Automation : public ctk::ModuleGroup {
On the other hand: I do not like the trick in this particular use case. You are disabling the OVC while the automation is ramping, but the user can re-enable it while it's still ramping. This is not good design. The appropriate solution for this is to create an input and a separate output and route the input through to the output during normal/manual operation but keep full control as long as we need it (i.e. during ramping). We have done it that way also e.g. for the FF and FB enable flags.