On 18 Mar 2014 04:01, Cathy Pinner wrote: > Can you remember what sort of clean up operation > you were doing when Legacy wasn't responding? Not > responding is different to freezing. Sometimes if > you leave a "non-responding" program for awhile, > it finishes doing whatever it was doing in the > background and starts responding again. I've > noticed this in Legacy and in other programs as > well. It's as if the program is sending the wrong > message to the computer. Rather than saying "I'm busy but still working hard"
When a program becomes non-responsive, it's generally Windows that determines this and changes the titlebar to reflect this. I could bore you all and tell you why Windows does this, but it's all down to a poorly designed program which is attempting to carry out a long-running task on the same thread of processing that should be handling the user interface. As Cathy says, leave it for a bit. Go and pour a glass of wine. If it's still not responding, then all you can do is open up the Task Manager and kill the program. -- Regards, Mike Fry Johannesburg (g) Legacy User Group guidelines: http://www.LegacyFamilyTree.com/Etiquette.asp Archived messages after Nov. 21 2009: http://www.mail-archive.com/[email protected]/ Archived messages from old mail server - before Nov. 21 2009: http://www.mail-archive.com/[email protected]/ Online technical support: http://www.LegacyFamilyTree.com/Help.asp Follow Legacy on Facebook (http://www.facebook.com/LegacyFamilyTree) and on our blog (http://news.LegacyFamilyTree.com). To unsubscribe: http://www.LegacyFamilyTree.com/LegacyLists.asp
