[deepamehta-devel] [Bug #13827] Deleted association still displayed

[admin at berlios.de]

Bug #13827, was updated on 2008-May-18 00:07
Here is a current snapshot of the bug.

Project: DeepaMehta
Category: None
Status: Open
Resolution: None
Bug Group: None
Priority: 5
Submitted by: x28
Assigned to : none
Summary: Deleted association still displayed

Details: Error scenario:
- created Topicmaps Test1 and Test2
- from Test1, created topics called Major, 1, 2, and 3
- associated 1, 2, and 3 to Major
- again from Test1, created topics 4 and 5 
- and associated them.

- In Test2, via search, revealed Major,
- via "What's related", revealed 1, 2, and 3
- via search, revealed 4
- via "what's connected", revealed 5.
- Then from Test2, connected 4 and 5 to Major, 
- then DELETED association between 4 and 5.

- in Test1, revealed the associations from 4 and 5 to Major, and everything shows correctly.
- In Test2, when asking "What's related" with 4, the result is correct: just topic Major
- BUT the visual map still shows two associations 
- when the association 4 to 5 is clicked, an error message shows:
  'Assiciation "null" can't execute command "selectAssoc" 
  (association "a-1191-1" not loaded)'


Follow-Ups:

Date: 2008-Nov-26 10:11
By: x28

Comment:
>  how could a sufficient 1st step solution look like for the user? 

As soon as an affected second map is refocussed, the user should be notified that it is no longer current. An example is MS XML Notepad 2007 that says "The file you are editing has been changed on disk. Would you like to reload this file?" I think the first half would suffice, and not asynchronously popping up but only upon user action. Something like "Some elements of this topicmap have been changed in the corporate memory. You may want to close and reopen it."

I have no idea how you discover this situation, though.
-------------------------------------------------------

Date: 2008-Nov-26 10:11
By: x28

Comment:
>  how could a sufficient 1st step solution look like for the user? 

As soon as an affected second map is refocussed, the user should be notified that it is no longer current. An example is MS XML Notepad 2007 that says "The file you are editing has been changed on disk. Would you like to reload this file?" I think the first half would suffice, and not asynchronously popping up but only upon user action. Something like "Some elements of this topicmap have been changed in the corporate memory. You may want to close and reopen it."

I have no idea how you discover this situation, though.
-------------------------------------------------------

Date: 2008-Nov-25 17:17
By: maltito

Comment:
maybe this could be fixed, more or less easily. i am not totally sure. when following this idea some questions arise. like,

* should there be a notification or should it just happen, cause the owner of the topic decided so?
* if notification, should it be interactive ? (ask for keeping a private copy of this assoc/topic) and how could this look like?

maybe we could make use of the messaging connection, which delivers the current collaborative notifications. atm, users of a workspace are notified if maps are published into workspaces or chats are opened. if a topic or assoc is really deleted, then a message could go out to all connected clients (which is not nice) and some of the temporarily opened views may loose a visible object (or n visible objects).

what do you think..
* what do we need for this on server/client side? 
* how could a sufficient 1st step solution look like for the user?

the solution has at one side to meet the needs of a very collaborative environment and on the other side, the personal needs of a user regarding his view (have all visible objects under conrol).
-------------------------------------------------------

Date: 2008-Nov-17 14:43
By: x28

Comment:
Thanks, Malte, for the workaround. However, the behavior contradicts the expectations raised by a philosophy that suggests that changes are always immediately effective without even saving some file! 



-------------------------------------------------------

Date: 2008-Nov-17 13:47
By: maltito

Comment:
i recognized this bug too and the current solution which worked for me is:

close the map i am working in and open it again out of my personal workspace.

no deleted associations are loaded again into your view.

-------------------------------------------------------

Date: 2008-May-18 00:24
By: x28

Comment:
Sorry, once more:
Error scenario:
- created Topicmaps Test1 and Test2
- from Test1, created topics called Major, 1, 2, and 3
- associated 1, 2, and 3 to Major
- again from Test1, created topics 4 and 5 
- and associated them.

- In Test2, via search, revealed Major,
- via "What's related", revealed 1, 2, and 3
- via search, revealed 4
- via "what's connected", revealed 5.
- Then from Test2, connected 4 and 5 to Major, 
- then DELETED association between 4 and 5.

- in Test1, revealed the associations from 4 and 5 to Major.
- When asking "What's related" with 4, the result is correct: just topic Major
- BUT the visual map still shows two associations 
- when the association 4 to 5 is clicked, an error message shows:
'Assiciation "null" can't execute command "selectAssoc" 
(association "a-1191-1" not loaded)'

-------------------------------------------------------

For detailed info, follow this link:
http://developer.berlios.de/bugs/?func=detailbug&bug_id=13827&group_id=5174