Force quitting any application should only be because the application is hanging or taking an extraordinary time doing some operation when you need to quit. The application needs to store information at the end of its session, and force quitting short circuits this process. Potentially, it could corrupt a file.
Not sure how it could corrupt a file. I would think the program would just become more unstable.
Well, you already know that it is wrong, but aside from the things you've mentioned, there is probably not much else to say.
You can look at the files in ~/Library/Caches/Adobe InDesign/.... and see if the InDesign Recovery directory is growing without bound.
Indeed, it will not preserve preference changes, workspace changes, keyboard shortcut changes, etc.
But I'd be surprised if there was anything truly horrible about it.
Thanks for all your opinions on this.
Yeah, I guess I can't really point to any hard facts about why it is "bad", to encourage the offendors NOT to do this. I wonder if there is any regular "clean up" of certain temporary files when the program quits that might remain when force quit is invoked. (They don't have a document opened when they do this.) I need an Adobe engineer to comment...
For one, temporaraly Lock files (idlk) will NOT be removed when any documents are open and can lead to problems on servers were a file looks like in use...
No one has documents open. They just do a force-quit as they think it's faster, and got into the habit when they were previously connected to our K4 server, and yes, there was a slight delay disconnecting from the server . Sounds like there's really nothing bad that happens to force quit (unless they've changed a preference). I was really looking for a convincing reason. Hard to convince others to change their habits.
I'm afraid sometimes InDesign crashes often enough that we might as
well Force Quit it regularly (and then a large fraction of the other
times it is indeed Force Quit because of interminable hangs). So I
guess, now that I think about it, I probably see more Force Quit
-equivalent exits than File > Quit exits. Becuase...why would you ever
Quit InDesign, anyhow?
Anyhow, so I guess if there was serious negative affect, I would probably
have seen it.
I am on a Mac 10.5.8 using CS4.
I find that closing down all network drives first then Indesign before closing down any other application helps, Indesign tends to shutdown better that way.
But if I was to try and close indesign first it tends to crash a bit. Not sure why and this could be just my set up here but thought I would mention it.
The problem is not getting users to stop force quiting to shut down InDesign faster, the problem is getting Adobe to fix the bug that causes InDesign to take so long to shut down in the first place.
My two cents,
I thought that in our situation, it's because we have a plug-in that connects to a K4 database, and the plug-in is communicating with that DB. When I don't have the plug-ins loaded, InDesign quits much faster.
I work on local files only, and I still have to either leave my desk for 10 minutes after I try to quit then shut down, or force quit and shut down. I do work on some large files though (50-100 meg catalogs) with lots of photos linked in. I guess it takes forever to clear all the cached memory or something. If I try to do a shutdown with InDesign open. I always get a time out error. Also when I go back to InDesign after working in Photoshop, FreeHand, Entourage or FireFox it takes a long time to redraw the InDesign screen and menus.
I also have a couple of indexing scripts, but don't run them often. Don't see how that would affect anything.
I read a post somewhere that you could change the "Live Screen Redraw" setting to help with the slowness, but I cannot find that setting in CS3. It may only be in later versions.
iMac 2.1 GHz PowerPC G5
Mac OS 10.4.11
1 GB DDR2 SDRAM (that's wierd, I thought I had 2 GB)
I believe this discussion is about Quitting InDesign, not Shutting down the machine. They are different things.
It is not normal for quitting InDesign to take more than a few
seconds. wkathym's situation is an exception, for a clear reason --
the K4 plugin.
It would be good, bjharrington, for you to isolate whether the problem
is with Quitting InDesign, or with something else as part of the
Not sure why you would ever shut your computer off, of course, but that's
a different story.
I am discussing quitting InDesign. I was just noting that I cannot shut down the machine until InDesign quits. The problem has been isolated to InDesign. I just ordered more ram, maybe that will help.
As far as the reason to shut down: company policy. I think the boss had something catch fire in the distant past. Now everything gets shut down every evening.
While I doubt more RAM is likely to help, we might as well wait and see, since debugging this stuff is pretty tricksy. Let us know how it turns out!
I doubt it also, but maybe it will speed up the redraw. That is more frustrating than the quiting problem.