[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[bug #4840] shouldCloseDocument flags seem to be ignored
From: |
nobody |
Subject: |
[bug #4840] shouldCloseDocument flags seem to be ignored |
Date: |
Sun, 19 Oct 2003 16:51:02 -0400 |
User-agent: |
Mozilla/5.0 (compatible; Konqueror/3.1; Linux) |
=================== BUG #4840: LATEST MODIFICATIONS ==================
http://savannah.gnu.org/bugs/?func=detailbug&bug_id=4840&group_id=99
Changes by: Fred Kiefer <FredKiefer@gmx.de>
Date: Sun 10/19/2003 at 20:51 (GMT)
What | Removed | Added
---------------------------------------------------------------------------
Status | In Test | Closed
------------------ Additional Follow-up Comments ----------------------------
This problem has been removed. What is left to decide is, wether the current
call from the document menu to close: should be replaced by performClose:
=================== BUG #4840: FULL BUG SNAPSHOT ===================
Submitted by: rburns Project: GNUstep
Submitted on: Tue 08/19/2003 at 08:35
Category: Gui/AppKit Severity: 5 - Major
Bug Group: Bug Resolution: None
Assigned to: FredKiefer Status: Closed
Summary: shouldCloseDocument flags seem to be ignored
Original Submission: implementing shouldCloseDocument in an NSWindowController
subclass to always return YES, and/or calling [self setShouldCloseDocument:
YES] doesn't have any affect. I think the flag is set correctly, but never
checked in _windowWillClose in NSWindowController.
Follow-up Comments
*******************
-------------------------------------------------------
Date: Sun 10/19/2003 at 20:51 By: FredKiefer
This problem has been removed. What is left to decide is, wether the current
call from the document menu to close: should be replaced by performClose:
-------------------------------------------------------
Date: Sat 08/30/2003 at 18:37 By: FredKiefer
This behaviour is actually correct, as long as the window hasn't set
isReleasedWhenClosed. Then the document and the window controller and the
window will hang around invisible. This does not make any sense to me, but is
acording to the spec.
The problem with the current implementation is that even when
isReleasedWhenClosed is YES, the window is not realy closed. I am working on
this in the moment, so expect this to be solved in a few hours.
-------------------------------------------------------
Date: Fri 08/22/2003 at 03:08 By: None
I've now got two apps. one that uses setShouldCloseDocument: YES], and another
that implements shouldCloseDocument to always return YES. and they both work
better now, but not quite right. The alerts get displayed as they should, but
the document still isn't being closed. ie. if I open a new document, make some
changes, and close the window, the alert will come up, and I choose "don't
save". the window closes. If I then go to quit the app, I will then get another
alert saying I have unsaved documents. I see that it now checks to see if it
can be closed, but is there a 'close' thats missing somewhere?
-------------------------------------------------------
Date: Thu 08/21/2003 at 06:33 By: rburns
Thanks, I will test this evening.
-------------------------------------------------------
Date: Wed 08/20/2003 at 14:04 By: FredKiefer
The problem here is that NSWindows perfromClose: method did not call
[NSDocument shouldCloseWindowController:], but a non existing method
[NSDocument windowShouldClose:]. I will change this now, so please retest if
this resolves your problem.
CC list is empty
No files currently attached
For detailed info, follow this link:
http://savannah.gnu.org/bugs/?func=detailbug&bug_id=4840&group_id=99
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- [bug #4840] shouldCloseDocument flags seem to be ignored,
nobody <=