With Imen we worked in an image were we generated some tags and browsed them in a tag browser.
Then we removed all the tags and generated some new ones.
From that point the tools started to crash, for example when we tried to propagate some classes from the query browser because some tags had no #mooseModel.
In the end we found out that we still had a Tag browser opened on the first tags somewhere. When we removed the tags it did not update this instance of the tag browser and it was propagating the tags on the bus I think. This caused us to get some tags that were normally removed.
Maybe we should have some announcements when we create/delete a tag and listen to them in the tag browser to refresh its content?
With Imen we worked in an image were we generated some tags and browsed them in a tag browser.
Then we removed all the tags and generated some new ones.
From that point the tools started to crash, for example when we tried to propagate some classes from the query browser because some tags had no #mooseModel.
In the end we found out that we still had a Tag browser opened on the first tags somewhere. When we removed the tags it did not update this instance of the tag browser and it was propagating the tags on the bus I think. This caused us to get some tags that were normally removed.
Maybe we should have some announcements when we create/delete a tag and listen to them in the tag browser to refresh its content?