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.
Product Version = NetBeans IDE Dev (Build 201111090600) Operating System = Windows XP version 5.1 running on x86 Java; VM; Vendor = 1.7.0_01 Runtime = Java HotSpot(TM) Client VM 21.1-b02 In this build (haven't seen this before), some files are opened multiple in the editor. Theses files are synchronized (see screenshot). If a file is changed, both tabs are colored blue. If unsafed, both are bold. I I safe one, both are displayed normal etc...
Created attachment 113071 [details] Screenshot
Created attachment 113073 [details] <no description>
It looks like issue #202681, but we can not close as duplicate according to https://netbeans.org/bugzilla/show_bug.cgi?id=202681#c7 which claims that change have to be done in C++ editor support, then it have to be done in Java editor support and so on for each language... FYI, it's side effect of new multiview components introduced in 7.1 (Source/History)
I don't know how this happened, I just monitored the problem. After closing all documents and re.opening a couple, everything had been ok. Usually I shutdown NB as is, with a couple of files open. Maybe this is a precondition for this problem? The problem occured on the first launch of the new build.
Can I ask for a help, what need to be done in java editor part, if anything.
I can see the problem at all. File can be opened multiple times by cloning the editor tab (right click on tab and select clone). If the editors are correctly synchronized all is fine.
Jiri, the issue is that tabs reopened after IDE restart are not correctly deserialized: Have a look at Jarda's evaluation: allEditors field in CppEditorSupport is empty after deserialization of first editor. It's an internal issue, right? While this bug and issue #202681 are user visible consequences.
pls read jarda's comment here: http://netbeans.org/bugzilla/show_bug.cgi?id=202681#c12
Are there deterministic steps to reproduce this with recent build? Or is it random?
No steps to reproduce, similar Bug #202681 evaluated as works for me -> Incomplete. If it occurs again, please reopen.