Is anyone else having this issue or am I the only one?
InDesign CS 7.5.2 now occasionally looses focus and hangs on opening INDD files from the file-->open menu. Ths can't be "normal operating procedure."
Yes, I've tried that. It doesn't work. I've even tried clicking at random places in the InDesign window, but the application will still lose focus and then hang after updating all the linked files.
Are you by any chance working on the dual monitor ?
Yes. 2 monitors @ 1680x1050. InDesign is usually on the right (secondary) monitor.
InDesign CS5.5 / 7.5.2 running on WindowsXP SP3 seems to hang when the program looses focus when a file is opened.
Manish is on the right track, I think. It only "seems" to hang. I personally would be dubious about running CS5.5 on WinXP, but when I was running CS2 and CS3 on WinXP I frequently experienced your exact issue - because there was a hidden dialog that I couldn't bring to the front, because the main ID window was locked by the dialog, and the dialog couldn't be dismissed with the keyboard.
It was a long time ago, so I don't recall which solution worked for me. I think I used MultiMon Taskbar to send the dialog to the other monitor where I could get at it. However, I know that ding quite well, and I'm pretty sure that ID isn't hung. Maybe Manish has a solution ready to go?
What joel said is right....
May be there is a Indesign dialog box which is popping up on the other monitor , hidden behind any other window , there are dialog boxes which pop up on the screen and are mandate , In these cases you will hear the ding and also the application would loose focus because at that time the dialog box is primary windows.
Also you wrote that the issue is at File-->open , does it also happen when you create the new file, if not then it could be windows link Missing fonts , Missing Links etc which could be popping on second monitor while opening the file.
you can try changing the primary monitor to other one.
Also you can check any dialog box popping up.
Interesting suggestions. There are no extra dialog boxes that may pop up under other windows because I only have a few files that I work with. They use standard a Windows font (Arial). There's a 100% chance that the file will open without hanging InDesign if I do NOT update any links, but click the "update" button drops the success rate down to 50%.
I'll have to try moving the program to the primary monitor. Thanks for the suggestions.
There's a 100% chance that the file will open without hanging InDesign if I do NOT update any links, but click the "update" button drops the success rate down to 50%.
I suspect that means that 50% of your InDesign files only need links updated (but ID knows where they are), while in the other 50% of your files, the links are missing or moved or rename, and your file-browser window (that gets spawned when you click "Update" but ID can't find one or more of your linked files) is behind your main InDesign window.
To prove this to yourself: Drop the second monitor for a few minutes. Unplug it entirely, go back to using just one monitor. Then use InDesign as you would ordinarily. Try to open your files. I feel pretty confident that you would experience 0 hangs-with-dings-whenever-you-try-to-click-anywhere-in-ID.
Question still stand....does it happen when you create new file?
forget about opening the file.....just create a new one , a fresh file ...save it and re-open it.
And yes what Joel said , disconnect one monitor and then check , it will sort the problem for sure as it will let you know what exactly is happening.
Hello all, sorry to bump such an old thread but this is the most similar topic I've come across to a problem some of us here are also having. I think the hidden alert is simply the update links progress bar, after playing with my monitors a bit:
but even with it active on the main monitor, the progress bar is stuck and cancel does nothing.
I have a theory that it is to do with linking to EPS files... but nothing to back that up.
This is InDesign CS5 and Win7
edit: I'm canvassing the other users here to see if it might be that file specifically.