-
Notifications
You must be signed in to change notification settings - Fork 167
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
After upgrade/uavo import, before reset: UI panes consider themselves unsaved #1871
Comments
The wizard should reboot at the end IMO, that would also result in automatically bringing up the setup wizard if you don't have actuator settings (although the upgrader still doesn't handle no settings properly either so that won't be perfect). |
Yes, but caution needs to be used here-- I think that reboot could race with commits if done naively currently |
Yeah, would be safe with a 5 second timer or something? |
I prepared a fix for this (tracernz@df0f763)... but I can't actually repro this with an import or an upgrade on current next (be3307d). Can you please try next, and if you can still repro, try that branch? |
I have a recent repro clicking through input stuff ---- will try to repro and check out your fix. |
Actually it's output stuff. |
I can still repro with the fix. Procedure: import a UAV file that changes actuatorsettings from defaults->nondefaults or vice versa. (Importing the same one doesn't trigger it!) Then click to output pane, then somewhere else. |
So, to note: the output pane is one of the few that doesn't auto-build relations. |
Another one: stabilization acts "unsaved" on connection of pipxtreme. My guess, the backing objects are missing and it calculates new values and seems unsaved. |
You're supposed to reboot anyways-- but if you don't, you get wonky results.
The text was updated successfully, but these errors were encountered: