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.
Summary: | Modes are propagated among projects - number of modes still rises ! | ||
---|---|---|---|
Product: | platform | Reporter: | Lukas Hasik <lhasik> |
Component: | Window System | Assignee: | mslama <mslama> |
Status: | CLOSED FIXED | ||
Severity: | blocker | CC: | dsimonek, mmirilovic |
Priority: | P2 | ||
Version: | 3.x | ||
Hardware: | PC | ||
OS: | Linux | ||
Issue Type: | DEFECT | Exception Reporter: | |
Bug Depends on: | 17995 | ||
Bug Blocks: | |||
Attachments: | patch18365.jar |
Description
Lukas Hasik
2001-12-05 15:50:32 UTC
I take this. CC-ing me The same on JDK 1.3.1_01. When project is closed all modes are closed too but not cleared from WorkspaceImpl. If user defined modes will be deleted when closed as suggested in fix of issue #17995 it will fix also this problem. To be sure to test also this case after #17995 is fixed I mark this issue as depends on #17995 not its duplicate. Previous comment was incorrect. This problem must be fixed in different way. We need to remove user defined modes just from WorkspaceImpl during project close not their XMLs from file system. So this is different from #17995. Currently fix of #17995 plus one change in WorkspaceImpl solves also this issue. Both fixes must be applied together. !! Attached patch contains fix of #17995 + #18365. !! Diff: [windows]> cvs di WorkspaceImpl.java Index: WorkspaceImpl.java =================================================================== RCS file: /cvs/core/src/org/netbeans/core/windows/WorkspaceImpl.java,v retrieving revision 1.85.2.2 diff -r1.85.2.2 WorkspaceImpl.java 657a658 > modeArray[i].setCloseOnlyInMemory(true); 658a660 > modeArray[i].setCloseOnlyInMemory(false); Created attachment 3730 [details]
patch18365.jar
I've tryed briefly this patch and it looks good. Modes are destroyed correctly and modes aren't propagated between(among) projects. WS even deleted unneccesary modes(created by user = hidden) which I copyed from older userdir. -I see only one remaining issue, if you undock FS tab from Explorer then order of tabs is changed even in a new created project. -I hope that I didn't miss something, this issue need longer testing... Few notes to changing order of tabs in Explorer: -undock filesystem, switch project(new), order changed -after restart, order is OK -switch to project with undocked FS tab and back, order is again changed.... Dafe, you forgot to mark this as FIXED in release33 branch verified in release33 and after applying patch into release330 too Resolved for 3.4.x or earlier, no new info since then -> closing. |