Changes between Initial Version and Version 1 of Ticket #638, comment 1


Ignore:
Timestamp:
21.03.2014 23:06:25 (6 years ago)
Author:
jri
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #638, comment 1

    initial v1  
    33I guess you edited the topicmap's "Name" child topic directly. In this case the change is neither propagated to the parent nor reflected in the GUI. While this might be considered a bug this is not the way a topicmap rename is supposed to be performed. 
    44 
    5 In general editing any child topic directly is not supported by DM. For example editing a Note's Text topic does not affect the Note. Edit the parent topic = the Note topic instead, at all works fine. Yes, this could be regarded an error in general. However I see it rather as a GUI design problem. The user should possibly not be able to edit any child topic directly. Implementing proper propagation of all the resulting changes would be too laborious from my view while providing no benefit for the user at all. 
     5In general editing any child topic directly is not supported by DM. For example editing a Note's Text topic does not affect the Note. Edit the parent topic = the Note topic instead, and all works fine. Yes, this could be regarded an error in general. However I see it rather as a GUI design problem. The user should possibly not be able to edit any child topic directly. Implementing proper propagation of all the resulting changes would be too laborious from my view while providing no benefit for the user at all. 
    66 
    77The user is supposed to edit the parent topic = the composite. The GUI should prohibit the user to edit child's directly, while the prohibition rule is not 100% clear to me. It's an open problem.