Community
Participate
Working Groups
models can not be edited from within a scenario as models can exist across projects. Either we need to block the operation (or actually allow the edit). RIght now it just fails which is very confusing to the users. Reported by Matthias.Filter@bfr.bund.de
Let's discuss on todays call. Maybe solution is to ALLOW the edit but either way we need the operation to make sense from a UI point of view. Right now it seems to allow the project edit but does not save the changes.
We allow edits of models (e.g. a disease model property) inside a scenario, and when saved it saves the changes. If it looks like it's not saving it is probably due to a refresh bug (312675) So the question is, if we allow edits (I think we should), do we: 1. Make a copy of the model in case the model is used within more than 1 scenario? 2. Change the model in all scenarios containing it? If 2, we can close this bug cause that's how it works right now. (Matthias, if it failed for you can you attach a stack trace?)
Stefan, I agree. The situation should be (and is) 2. Change the model in all scenarios containing it? so..., we can close this bug cause that's how it works right now.
I agree we should close, but let's confirm with Matthias who reported the bug first.
Hi all, we discussed the issue and would suggest the following: We can leave the situation as it is, but there should be a detailed warning to the user when saving the changes. We think the best would be to explicitly name all the dependent structures that are affected by the changes within that warning. Matthias
Hi Matthias, I think that's a great idea. Actually, the code that finds all the dependent object after a save is already there (it's used to refresh those objects), so adding the warning dialog should be easy. I'll fix this, but probably not before the 1.1.1 release (I put 1.2 as target).
We discussed this on the STEM call today. Decided to lower priority (this is a new feature request) and the suggestion was to implement it in a less obtrusive manner by: 1. Creating a new view displaying a log of dependent objects affected. 2. Perhaps not invoke the check during every save but rather add a menu option "Show Dependencies" or equivalent.
A feature to show all objects in the workspace that references a given object has been added (right-click and select "Show References"). I will close this bug, let me know if anybody objects.
