Skip to content
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

Wrong clipping of edges in Mondrian #229

Closed
seandenigris opened this issue Aug 3, 2015 · 6 comments
Closed

Wrong clipping of edges in Mondrian #229

seandenigris opened this issue Aug 3, 2015 · 6 comments

Comments

@seandenigris
Copy link
Contributor

Originally reported on Google Code with ID 229

Do the following:
- import all Glamour packages in Moose
- select all packages
- invoke Visualize/Package-Wise System Complexity
- do not maximize the window, but just scroll from left to right
- as you scroll from left to right, some of the nested edges (that come from the classes
from the top 
Kernel package) get removed from the view even if at least one of the nodes are in
plain sight

Reported by tudor.girba on 2009-11-22 10:52:30

@seandenigris
Copy link
Contributor Author

I cannot reproduce this issue.
Edges disappear when I wave the mouse over the picture. The balloon bubble seems to
erase them. Refresh is 
not done properly. But is it the same problem?

Cheers,
Alexandre

Reported by alexandre.bergel on 2009-11-25 18:04:07

@seandenigris
Copy link
Contributor Author

The first attached picture reveals the problem.

Reported by tudor.girba on 2009-11-28 01:58:25


- _Attachment: second-window-misses-an-edge.png
![second-window-misses-an-edge.png](https://storage.googleapis.com/google-code-attachments/moose-technology/issue-229/comment-2/second-window-misses-an-edge.png)_

@seandenigris
Copy link
Contributor Author

Also, it appears that sometimes, when we select another window, some edges tend to disappear,
too. The 
attached picture shows the problem (compare it with the one from the previous comment).

Reported by tudor.girba on 2009-11-28 01:59:48


- _Attachment: with-the-second-window-selected.png
![with-the-second-window-selected.png](https://storage.googleapis.com/google-code-attachments/moose-technology/issue-229/comment-3/with-the-second-window-selected.png)_

@seandenigris
Copy link
Contributor Author

Reported by tudor.girba on 2009-12-03 15:18:04

@seandenigris
Copy link
Contributor Author

Looks like this issue was somehow solved in the process of fixing the zOrder. The problem
used to appear even 
by simply spawning a popup over a set of blueprints: the invocations between classes
would not be redrawn.

Reported by tudor.girba on 2010-01-27 10:54:14

@seandenigris
Copy link
Contributor Author

I declare it fixed. We reopen it if the issue resurfaces.

Reported by tudor.girba on 2010-01-30 00:57:52

  • Status changed: Fixed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant