Status: New Owner: ---- Labels: Type-Defect Priority-Medium
New issue 934 by alan.mcn...@gmail.com: Moose Meta Browser - Entities panel not updated when selecting Entity in Map http://code.google.com/p/moose-technology/issues/detail?id=934
In the Map panel it is possible to select a box representing an Entity. When this is done, the Entity and its relationships are highlighted in red in the Map pane.
Also, the Relations / Properties and Comments panes are updated with information for that Entity shown.
However, the Entity pane is NOT updated.
I would expect that the Entities pane would be changed so that the Entity selected in the Map pane would also be selected in the Entities pane, including expanding any Entity hierarchy as required.
Comment #1 on issue 934 by tu...@tudorgirba.com: Moose Meta Browser - Entities panel not updated when selecting Entity in Map http://code.google.com/p/moose-technology/issues/detail?id=934
I cannot reproduce this on 4.8. On which version did you try?
Comment #2 on issue 934 by alan.mcn...@gmail.com: Moose Meta Browser - Entities panel not updated when selecting Entity in Map http://code.google.com/p/moose-technology/issues/detail?id=934
More information - this only error occurs when the Entity is filtered on a tag.
This error does not occur when the Entity is not filtered on a tag. This error does not occur when the Entity is already displayed within the filering (see attached PharoScreenshot3.png)
In the attached example, I have first clicked on the Dude tag to filter on the flag, then on FAMIX.Type in the Map.
As you can see (attached as PharoScreenshot.png), the Entity panel does not expand or remove the filtering to show the selected FAMIX.Type
Yes - hard to say if this is incorrect behaviour or not. Just unexpected on my part.
Attachments: PharoScreenshot.png 346 KB PharoScreenshot.3.png 351 KB
Updates: Status: WontFix
Comment #3 on issue 934 by tu...@tudorgirba.com: Moose Meta Browser - Entities panel not updated when selecting Entity in Map http://code.google.com/p/moose-technology/issues/detail?id=934
The current is behavior is reasonable. I will mark the issue as won't fix.