-
-
Notifications
You must be signed in to change notification settings - Fork 18
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
6.6.2: Settings can't be changed by going back #561
Comments
Thanks. I can reproduce that. On already created "sessions" it does not apply the changed settings. Not for myself: this has something to do with the |
I see now that you are talking about generating projects. I cannot reproduce the problem there. What I can reproduce is on the import of models or transfer files, but I'm not sure how to solve it. I tended to go for the approach to recreate all the sessions, but this would lead to unexpected behavior when only a model changed. So I vanished this approach. So first thing is to fix, that it does not update the settings. Then the behavior would look like this:
So there could be the approach to recreate the session when the db changed (but not every setting):
|
Hm... something I forgot in the description above. Having Model "Kbs1" and "Kbs2" checked (1) -> next: run the session for "Kbs2" (2) -> back: "Kbs2" is now grayed out (because existing in the DB) (3) -> next: only session for "Kbs1" is visible (4) What about skipped? So two fixes required:
|
… with the current settings. But do not reload existing skipped session-widgets of another database. So the identificator now checks the database as well. This fixes #561
Behavior:
So there's no way to change the path unless you close the wizard and start it new. This should be fixed.
The text was updated successfully, but these errors were encountered: