-
Notifications
You must be signed in to change notification settings - Fork 69
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
JSIActionGroupSwitch plugin action / forcedShutdown interaction #392
Comments
Maybe-fix (untested): https://www.dropbox.com/s/apttlrrfarqktvo/RasterPropMonitor-dev.0.23.1.zip?dl=0 |
ill test it now |
doesn't work |
Okay. Looks like the easy answer wasn't the right one. I'll have to put some more time on it. |
I suspect it has something to do with the mastervariable as I think it worked before I added that |
but it didn't deliver the needed results |
Okay. My new working theory is that it's an interaction between the trigger event and the action group switch. I will have to instrument that code better so I can really see what it thinks it is doing. |
Do you think it would be possible to be able to transfer a persistent variable to a different persistent variable? I ask this because I have an icon on my altimeter bar that displays the selected altitude. It moves up and down as I increase and decrease the target altitude. I want it to stay where it is until I update it with a new altitude. |
It is possible. Not yet, but maybe soon. |
Another maybe-fix: https://www.dropbox.com/s/apttlrrfarqktvo/RasterPropMonitor-dev.0.23.1.zip?dl=0 However, I think what you're trying to do does not require the trigger event. What you need to do is use the masterVariableName / masterVariableRange to indicate when the switch should be enabled. For example:
This is my switch for enabling the Gemini docking radar in my FASA Gemini pod. The switch will not work as long as the custom variable is false (=0). When the custom variable is true (=1), the switch functions normally. If the switch is on and the custom variable becomes false, the switch turns itself off again, and it stays off. |
Not sure about that. I already thought of that before. I'll try it again with the new build. |
Fixed! Thank you! |
When the plugin normally queries state from its state variable, we need to override that behavior for forceShutdown. Fixes issue Mihara#392.
Spawned from #385 - if we try to force a plugin action off, it ends up ignoring the "force it off" statement, instead using the current state of the plugin.
The text was updated successfully, but these errors were encountered: