This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 213141 - Document does not have up-to-date content immediately after reload
Summary: Document does not have up-to-date content immediately after reload
Status: RESOLVED WONTFIX
Alias: None
Product: platform
Classification: Unclassified
Component: Text (show other bugs)
Version: 7.2
Hardware: All All
: P3 normal (vote)
Assignee: Miloslav Metelka
URL:
Keywords:
Depends on:
Blocks: 211358 228826
  Show dependency tree
 
Reported: 2012-05-29 08:58 UTC by Tomas Mysik
Modified: 2013-06-04 09:37 UTC (History)
3 users (show)

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
unit test (4.28 KB, application/octet-stream)
2012-05-29 08:58 UTC, Tomas Mysik 		Details
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Tomas Mysik 2012-05-29 08:58:04 UTC 
Created attachment 119982 [details]
unit test

If one saves document and immediately copies new content via streams, document still contains the old content.

Unit test attached, I hope it is correct :)

Thanks.

Product Version: NetBeans IDE Dev (Build 20120528-3c75442ef118)
Updates: Updates available
Java: 1.6.0_32; Java HotSpot(TM) 64-Bit Server VM 20.7-b02
System: Linux version 3.4.0-030400-generic running on amd64; UTF-8; cs_CZ (nb
Comment 1 Jaroslav Tulach 2012-06-01 22:21:43 UTC 

*** This bug has been marked as a duplicate of bug 207060 ***
Comment 2 Tomas Mysik 2012-11-07 08:59:09 UTC 
Have to reopen, it does not seem to be fixed - at least the test still fails for me. Can you please verify, Jardo?

Thanks.

Product Version: NetBeans IDE 7.3 Beta 2 (Build 201211052012)
Updates: NetBeans IDE is updated to version NetBeans 7.3 Beta 2
Java: 1.6.0_35; Java HotSpot(TM) 64-Bit Server VM 20.10-b01
Runtime: Java(TM) SE Runtime Environment 1.6.0_35-b10
System: Linux version 3.2.0-32-generic running on amd64; UTF-8; cs_CZ (nb)
Comment 3 Jaroslav Tulach 2012-11-07 14:39:25 UTC 
Thanks for the test. The FileChange event is delivered as soon as the stream closed and is synchronously passed to CloneableEditorSupport as PROP_TIME change. The support detects it needs to reload. Then it however starts to switch between EDT and outside of EDT, so it is not easy to find out the document has already been refreshed.

Passing to openide.text...
Comment 4 Miloslav Metelka 2012-11-12 13:52:34 UTC 
Btw getting the content of editor in the test should definitely be done in Document.render().
The reload is done in AWT since the caret position needs to be restored after the reload which has to occur in AWT.
In the future we could think about doing the reload by applying diffs between current editor's content and the loaded content which could possibly eliminate  need for a caret update but it is rather a thin ice.
So I close this as wontfix. I guess that getting the content in invokeLater() would probably work (since the reload task would already be in the AWT queue) if it would work for you as a workaround for your usecase.
Comment 5 Tomas Mysik 2013-06-04 09:34:01 UTC 
BTW workaround for this issue (at least for me) was to add a sleep() for 1 second.