search

0xCAB / idocit

Automatically exported from code.google.com/p/idocit
0 stars 0 forks source link

Text changes don't make the iDocIt!-editor dirty #3

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
What steps will reproduce the problem?
1. Open the example WSDL-file (Ebay Trading API).
2. Navigate to the "GetFeedback"-node in the TreeViewer.
3. Change the documentation-text on the left for the thematic role "ACTION.

What is the expected output? What do you see instead?
The iDocIt!-editor should be marked as dirty since its contents have been 
changed by the user. The dirty-state should be visualized with a "*" in the 
editor's title. But the editor is not marked as dirty. After selecting another 
node in the TreeViewer, the editor is marked as dirty.

Original issue reported on code.google.com by krauseda...@web.de on 14 Apr 2011 at 7:26

GoogleCodeExporter commented 8 years ago 
Estimation: 2 hours

Original comment by dirk.mei...@gmail.com on 27 Apr 2011 at 8:29

GoogleCodeExporter commented 8 years ago

Original comment by krauseda...@web.de on 17 May 2011 at 5:27

GoogleCodeExporter commented 8 years ago

Original comment by dirk.mei...@gmail.com on 17 May 2011 at 11:10

GoogleCodeExporter commented 8 years ago 
Now a thread checks every 1.5 seconds if changes were made in the text field 
and if there are changes the ChangeEvent is fired to inform the higher 
composites about the that and the editor becomes dirty.

Original comment by dirk.mei...@gmail.com on 17 May 2011 at 1:41

GoogleCodeExporter commented 8 years ago 
Problem:
If a signature element has no documentation and the first one is added. Then 
enter the text field and a NPE is thrown.
The thread tries to update the documentation from the selection object which is 
null.

Original comment by dirk.mei...@gmail.com on 18 May 2011 at 7:58

GoogleCodeExporter commented 8 years ago

Original comment by dirk.mei...@gmail.com on 18 May 2011 at 8:09