[BLUEJ-69] uses arrows are not removed when they should
this whole thing needs to be re-thought... \- when should they get removed?
------- Comment BLUEJ-1 From Michael K?lling 2000-12-14 12:27:52 [reply] -------
*** Bug 136 has been marked as a duplicate of this bug. ***
------- Comment BLUEJ-2 From Scott L. Bain 2002-09-21 06:20:31 [reply] -------
The uses arrows should be removed when one object no longer holds a reference to another. For instance, if ClassA has a member of type ClassB, then the arrow should show. If this member is removed, the arrow should be removed as well.
If this is too difficult, one should at least be able to "refresh arrows", which would cause BlueJ to remove all the arrows and re-establish them correctly for the code at the current point in time.
This comes up a lot when refactoring.
Issue metadata
- Issue type: Bug
- Priority: Medium
- Fix versions: 4.0.0