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: | PropertyVetoException on unmount FileSystem | ||
---|---|---|---|
Product: | platform | Reporter: | pzajac <pzajac> |
Component: | -- Other -- | Assignee: | akemr <akemr> |
Status: | CLOSED FIXED | ||
Severity: | normal | CC: | prgsust |
Priority: | P3 | ||
Version: | 3.x | ||
Hardware: | Other | ||
OS: | All | ||
Issue Type: | DEFECT | Exception Reporter: | |
Attachments: | Exception stacktrace |
Description
pzajac
2000-12-01 20:00:56 UTC
Created attachment 362 [details]
Exception stacktrace
What build? (Please set the Version field too, unless this is really in 3.0.) I've assumed version was reported wrong. Changed to 3.1 It's working ok for me (w2k, [stable31-24]) Should we change Platform/OS if it still appears? Or is it working ok elsewhere now? Exception is not thrown but the behaviour is still not what the user would expect. When you choose "Cancel" in the dialog that prompts: "File is not saved, Save ? >Yes >No >Cancel" it cancels closing file but it unmounts the file system. Then you can still edit the file but the filesystem is not in repository. I suggest better fix: before unmounting FS check whether it contains some modified Data Objects and if so, show dialog similar to the one that appears when you choose File|Exit (when you have modified files). It can be fixed in org.netbeans.core.actions.UnmountFSAction, take a look at org.netbeans.core.NbTopManager.exit(). org.netbeans.core.EditDialog can be reused, needs to be slightly extended to accept FS as a parameter and diaply only modified files on that FS. Fixed in main trunk and 3.1 Before unmounting filesystem(s) appears similar Save dialog to the one that appears when you choose File|Exit, which will display modified Data Objects - You can choose Save, Save All, Discard All and Cancel. If you choose Cancel on this dialog, filesystem won't be unmounted. [NetBeans 3.1 build #28] [Main trunk build #89] verified NOTE: Bug still appears in version : FFJ20 Resolved for 3.4.x or earlier, no new info since then -> closing. |