TM->FT:Due to the fact, that this one is an enhancement...please have
a look. Thanks !

*** Issue 2883 has been marked as a duplicate of this issue. ***

Please fix this. This is a really bad design and has no user-
friendlyness logic in it. We want to close documents and not close 
OO. If we wanted to close OO we would do so. Take the behaviour from 
MS word, you can have word open with no documents.

Sorry - but it`s not right what you say. If last document will be
closed a timer starts and you have 5 sec to open a new document by
clicking a file in your system file browser. Only if this times out
the office realy shutdown. But it checks for new incoming files before
it dies.

If you needs more then 5 sec (e.g. 20 min) I think it`s not a good
idea to hold the whole office in memory for this time. Because such
office can`t be used by any UI then. It would waits for any requests
of the OS to open an office registered document - but may be for ever.
And the user lose xx MB of RAM ...

On the other side: It doesn`t matter if office shutdown then. Next
loading will be mutch faster then the first one. Because all
neccessary libraries are already loaded by the OS and may be cached
(if time isn`t to long).

And last but not least. Under windows you have the option to use our
quickstart application. It prevents such shutdown on closing last
document. And if I`m right informed - such tool was developed by the
openoffice community for unix too.

You say: exit entry is annoying because sometimes you close the whole
application but wouldn`t do so. I know many applications which
provides such behavier. (browsers like mozilla, IE) And here we must
decide: without the possibility to exit we can have an automaticly
exit on closing last document only (if we doesn`t provide an extra GUI
for that). 

Further I think we shouldn`t show nervous message boxes on every
closing of last document. There exist better solutions (e.g. quickstart).

In general it`s a question of system integration. If we can make our
startup much faster it should be possible to react for system requests
to open registered office documents only. Every document window should
be closeable by himself. Last one force a shutdown on closing.

There are quickstart-Applications for the gnome-panel 
http://ooqstart.sourceforge.net/
and for kde 
http://segfaultskde.berlios.de/oooqs/
I didn't try these out myself but they are reported to work pretty
well. If you got lots of physical RAM you may want to give it a try.
Maybe there are more out there - I don't know

Andreas: the mozilla example you provide is not applicable to OO. 
When you close the last open windows, it means you want to close the 
application. Browsers dont have an option "close window" (except 
opera)

When we click on close document, we want to close the document, not 
close openoffice. If we would want to do that, we would click on the 
X or just exit. It's as simple as that.

Name me any other office suite that closes the program when you close 
a document.

-I havent seen such a timer. If i close the document, it exits and 
that's it.

-The argument that the second openoffice load will be much faster is 
not a valid argument to leave this behaviour unfixed.

-We dont want to use a quickstart feature, eating tons of ram, just 
to be able to keep oo open when you close the last document

This is a standard behaviour of ALL office suites. Come on, user 
logic in most of the time says we are working on a doc, finish it, 
close it and want to open/begin a new app. Why should the app be 
closed? Is this that difficult to implement?

1)
Sorry again - Please install a mozilla on your disk. You will find a
menu entry for "file->close" and one for "file->exit". Exactly the
same as in our office. First one closes the browser/office window ...
and in case it was the last one - it close the whole application too.
Last one close the whole application - true for mozilla and for our
office.
PS: The window close button does the same like "file->close".

2)
I`ve implemented this timer and know: you have 5 sec - no more.
Note: The office has no UI during this time but it exists in memory.
Please open a task manager to see how long the office resists in
memory after closing last document ... or for calling "file->exit".

2)
You will not use the quickstart module - because it "eats tons of
ram". But you wish to leave the office inside memory after closing
last document. But then you have a full featured office inside ram
without the chance to kill it - expect you use any task manager tool
to do so.
You can`t have a living office without using ressources.

3) "Name me any other office suite that closes the program when you close 
a document." ... it should be read: "Name me any other office suite
that closes the program when you close 
THE LAST document." By the way: We are not "other office suites". Why
every application must be like any other one. Then we doesn`t need
many companies with different tools - then we need ONE BIG company
with ONE OFFICE. But then we have to pay for it more then now -
because there is no competition.

4)
Ok you are right. A user whish to open a document, work on it and
close it - open another one ... and so on. And that`s the intention of
our office. You haven`t any desktop any more. You should use your
system file browser to open documents. Our office react for such
requests and finish his work if you close the (last) document - or
stay tuned inside memory by using the quickstart module.
That means from user logic: "Don`t thinking about applications - think
in documents".

1)Mozilla != Office Suite. We want to open links in new windows so we 
can go back and forth in a webpage. You cant compare an office suit 
behaviour with a browser suite. Period.

2) So, how is it useful that it stays in ram if i need to relaunch 
office to continue working? Just because it is going to save me some 
seconds loading up? If the UI stayed on for those 5 seconds, i would 
SAVE ALL THE SECONDS i need to relaunch office!!!

3) (you mistakenly didn't add up)
I can kill any other office app by opening File->Exit or just hit the 
X. Why is this so hard to understand? We want to tell office when to 
exit, we dont want office to decide that for us.

4)
You say something like "if all office suits are the same then there 
would be no competition"
I am not asking oo to be like ms office. I am asking that you correct 
a logic design flaw that ALL other suites do fine. Don't reinvent the 
wheel

5)
Use my system file browser? That would work for existing files, 
though it would be slow and lame to open my file browser because a 
design flaw closes oo when i didn't ask. I even though it was 
crashing at the first time because my mind didn't even consider the 
posibility of a design flaw on something so trivial.

Conclusions:
If i am working on a document and finish it, hit close (being the 
only one open) and i want to open (existing or NEW document) i must 
do one of the following:
-Open the new/existing one with the other one open. This is lame for 
an office suit and expected behaviour for a browser. Why? Because 
when we are on a webpage we type the new link and it _overwrites_ the 
current window. If oo would overwrite the existing window (which is 
not logical, it should open a new one like it does) then this rfe 
would not be an issue
-Be ultra fast and looki for the oo icon or type soffice so fast in 
less than 5 seconds or else load all office from scratch. Yes, this 
is reaally soo cool (sarcasm)

P.S I love your suite and i am making a positive criticism that would 
improve the suite. Besides, i did not post this rfe (care to think 
most users would feel this way?) but i heavely back this since i 
though oo 1.0 was crashing less than 5 min after i installed it

In a webbrowser if you have one window open looking at an old page and
you want to go to a new page you can select a new url for that window
and the previous "document" is discarded and replaced with the new
page. If you want the new document to open in a new page you do it
explicitly by first creating a new window and then using "open
document" in that window

In writer if you have one document open and want to open another then
writer always behaves like a browser's new window + open document. If
you have one document open and want to discard it and start a new
document to replace it you have to indeed open a new document and then
close the old one. Which is awkward, and I dislike it myself.

So...
One suggestion is to always open a new document in the existing frame
and close the existing document to replace it unless explictly asked
by the user to open the new document in a new frame ( perhaps here
when you would normally get "save changes" vs "discard" if the to be
replaced document has had modifications you could have "save changes"
vs "discard" vs "open document X in new frame" :-) ). Now you have
almost exactly the same situation as mozilla. Mozilla users don't
complain about the last close exiting the application because they
asked the application for the extra windows explicitly and mentally
take responsibility for those extra windows themselves. In our case
users get an extra window every time they open a document, so all
these extra windows are something that staroffice created and users
probably
expect staroffice to manage them entirely.

The alternative suggestion is to make the "close" a "close document"
not a close window. When the last document is closed either 
a) A popup says "last document closed, exit application or launch new
document ?" (maybe with an option to default this to exit immediately)
b) The last document closed is replaced with a new document and the
frame itself not closed. Which would forcd users to actually use exit
application when they want to close the last document (doesn't really
make a lot of sense when considering a windows close frame "X", but
see MS hackaround)

The ms office XP approach boils down to something like b, where each
windows has the normal close x on the top right and if you use that x
usually then you run into the exact same snag that writer users have
with this. So all the XP users use the little x in the top right of
the document window which is a window of its own inside each toplevel
frame, and this one acts like b above in that normally when clicked it
closes the frame like the normal outside X but when the last document
is closed its containing frame goes blank, but the toplevel frame
doesn't close at all.

I think the browser 

...style approach might be interesting. 

issuezilla must have limited the length of text

*** Issue 5878 has been marked as a duplicate of this issue. ***

I think the argument should not be if the current behaviour of OOo 
is "illogical" or "inconsistent". In fact, I think it is quite 
logical and consistent: 
* Each OpenOffice.org window can contain exactly 1 document, no more 
and no less (consistent).
* The difference between "Exit" and "Close" is that "Exit" closes all 
OpenOffice.org documents/windows, and "Close" closes just the active 
document/window (logical). 
* It is just that when there is only one window left, both come down 
to the same thing.

IMO, the key to this feature request is the way users often work: 
they close a file, and want to immediately open another one for 
editing. It is then convenient if (the menu bar of) the window is 
still in view, in the same place on the screen, as your eyes are 
already on that spot and your mouse pointer is nearby, so you can 
quickly reach the menu FILE->OPEN. Other ways to open a new OOo 
window (quickstarter, start menu) are not in direct view, require 
more mouse movement, etc.
Another frequently occurring use case is to close a document and 
immediately start to work on a new blank document. 

Therefore I repeat my suggestion: if FILE->CLOSE is used to close the 
last remaining OOo window, OOo should automatically open a new window 
taking its place (it should contain a blank document of the type last 
edited). FILE->EXIT would still simply close the last window.
While not sacrificing logic and consistency, this would add the 
desired conveniency. 

*** Issue 5648 has been marked as a duplicate of this issue. ***

*** Issue 7539 has been marked as a duplicate of this issue. ***

I agree with Simon about this whole issue. The current behaviour of
OOo when closing the last document is confusing to users, and a waste
of time. Keeping the Quickstarter open is a waste of RAM (About 20MB
on my in-laws Windows XP machine), especially if one only uses OOo for
a couple hours per day.

So, to keep this short and sweet, how about this little chunk of logic:

If the user chooses "close" AND this is the last document, close the
document and create a new, blank document (or just keep the toolbar
active)
If the user chooses "exit", check the modified status of any open
documents, prompt to save if necessary, then exit the entire application.

It's not perfect, but I'm not actually a programmer, despite going to
college to become one.

I endorse the proposal of Simon & Dion, too.
IMHO, the best idea would be to add a check 
box like 'Keep OOo open after closing all documents' to the options... With this 
option set, an empty framework with the toolbar still active should remain open after 
CLOSING all documents. If the user selects EXIT, OOo should exit completely, of 
course.

PS: Platform/OS should be 'All'.

Matthias, you sent the proposal.
http://ui.openoffice.org/servlets/ProjectDocumentList?dcID=630&action=download
Would you like to take care of the issue? Thanks, Stefan.

reassign issue

working on spec

*** Issue 8450 has been marked as a duplicate of this issue. ***

Summary: close file exits program
                Component: word processor
                  Version: 1.0.0
                 Platform: Other
                      URL:
               OS/Version: other
                   Status: UNCONFIRMED
        Status Whiteboard:
                 Keywords:
               Resolution:
               Issue type: DEFECT
                 Priority: P3
             Subcomponent: code
               AssignedTo: sba@openoffice.org
               ReportedBy: davidsyes@openoffice.org


Closing the next to last, or even the last open document causes the program to exit.

Behavior expected of "Close" is that "Close" should close documents only, not exit/terminate the application.

When "Close" occurs, the user should see either a file-open dialog, or a dialog listing the recently opened files. A WYSIWYG portal or file-based bitmap 
should display so the  user can distinguish similar versions of a file without opening each one. If the user hits the escape key, these dialogs should go 
away and the user should see a skeletal/minimal Writer canvas. At this point, the user can use the menu to open files, alter appropriate defaults, or exit 
the application.

Behavior expected of "Exit" is that "Exit" should close the open, saved files, alert that any unsaved open files need to be saved, saved-as, or aborted, or 
the action cancelled. Application exits only when the USER says so, via these conditions.

This issue was reported earlier this year, or late last year, but I could not find it using exactly the 4 words I used above.

http://ui.openoffice.org/proposals/File_close_behavior.sxw

partly implemented, to be continued

*** Issue 9332 has been marked as a duplicate of this issue. ***

*** Issue 10358 has been marked as a duplicate of this issue. ***

*** Issue 12212 has been marked as a duplicate of this issue. ***

fixed for OOo1.1

closed 

I would like this issue to be reopened.

Please allow me to describe what just happened:
1. I was working on a drawing..
2. I open calc and read some data from the spreadsheet.
3. No longer needing the spreadsheet, I click File and Exit.
4. "Hey, where is my drawing?"
5. Looking on the taskbar: "what the h*ll happened to my drawing?"
6. "Damn, version 3.2 is still THAT unstable?!"

IMHO it is rather odd to implement File-->Exit and File-->Close the way they are
now. No matter what you think about it, I (and many, many people with me)
consider it a bug. And I think it rather stubborn to keep it working this way
even after so many people reporting this issue.

Please just do a search for "file exit" issues and take a quick look through the
titles of the issues that come up. Please realise the vast majority considers
this a bug (or a crash even!!).
To be honest, I was quite surprised that version 3.2 contained such basic errors
(yes I also thought it a crash of the framework) and after learning that this
bug was actually a "feature", I was completely baffled that version 3.x still
contains such questionable UI design.

Clearly all those people reporting this issue can't be wrong! And if you
absolutely MUST have it your way, then for heavens sake make it a setting, but
please fix this thing. It just looks like a bunch of amateurs hacking away on
OOo the way it works now. Yes, it almost looks like it is a bug (some kind of
crash) that noone seems to be able to fix somehow.

Imagine someone making a suite of media players in which a piece of music would
be played in an other window than a movie would. So you are playing some music,
then opening your movie player, starting the dvd, and then closing the music
player because you no longer need it. Would you want the movie player window to
close too? Why not? It comes with the same set of applications.
Would you want to close all virtual machine windows when you shut down one
instance? Why not? It is the same application even!

Sorry for going on and on about it, but I'm trying to make it clear how little
sence it makes the way it is implemented now. Please fix it.

Anyway.. Here's a suggestion: Rename the current "Exit" menuitem to "Close all
OOo windows" and make a new Exit at the bottom that only closes the window from
which the user opened the File menu. The way the "Close" menu item works now (a
blank background in a generic OOo window with an option to create a new document
of any supported type) is fine with me. I hardly ever use that function anyway,
but it seems more sensible than closing the window entirely.