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: | Selecting "quit" from the NetBeans application menu does not prompt to save modified files, etc. | ||
---|---|---|---|
Product: | platform | Reporter: | rsutphin <rsutphin> |
Component: | Window System | Assignee: | Tomas Hurka <thurka> |
Status: | VERIFIED DUPLICATE | ||
Severity: | blocker | CC: | mslama, pzavadsky |
Priority: | P3 | ||
Version: | 3.x | ||
Hardware: | Macintosh | ||
OS: | Mac OS X | ||
Issue Type: | DEFECT | Exception Reporter: |
Description
rsutphin
2003-06-07 20:52:05 UTC
Reasssigne to Tomas for investigaion. I know about this API, but I don't want to add platform specific code into Netbeans code base. I can understand the no-platform-specific code stance, but this is a pretty serious thing -- if you log out/restart/shutdown and you have unsaved changes in NetBeans, those changes are silently lost. At the _very_ least this should be documented in mile-high letters-of-flame in the OS X readme and/or FAQ. (I presume that this doesn't happen on Windows or Linux, though I haven't tried recently. If so, what's the mechanism that they use and why doesn't it work on OS X? Is this another Apple JRE bug?) You are right, I will add it to the NetBeans How to page. This problem does not happen on Linux or Windows, since there is no additional Menu, where you can select 'Quit NetBeans'. Because Window System v1 will not be supported from now by our team, all old winsys issues (now "core/window system v1" issues) are going to be closed as WONTFIX. Changes in API which emerged both from UI spec and problems with adjusting to the older API are described in the document http://core.netbeans.org/windowsystem/changes.html. It shows also recommends how the client code should be adjusted to the new window system. If you think this issue apply also to the new winsys then change the subcomponent (to "core/window system") and REOPEN it. issue doesn't apply to new window system - verified This issue has nothing to do with new window system. *** This issue has been marked as a duplicate of 39780 *** verified duplicate |