Interesting description. Sounds similar to a non-MS app I automate which does something similar. If closed from Python everything works fine; however, if user closes app before Python the next time it's launched it opens hidden and user can't see it at all. The only partial work around I've found is to use a certain routine in that app to detect the condition and enum the toplevel windows to find and kill the pid of the hidden app. Sounds awfully similar. Is the Excel issue definitely a MS one I wonder...just thinking out loud.
Bobby -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Bob Gailer Sent: Thursday, August 17, 2006 4:37 PM To: [EMAIL PROTECTED] Cc: python-win32@python.org Subject: Re: [python-win32] Excel corrupted display problem [EMAIL PROTECTED] wrote: > Hi list, > > I have a Python script that pops up Excel, fill it, > and then continue. If the user clicks on my Python > side to close Excel (via a call to the Quit() > function), then I can reopen it later via another > dispatch call and so forth. > > However, if the user close Excel from the Excel side, > next time Python side starts Excel again, the Excel > display area (the area where the spreadsheet cells > goes) is screwed up. The rest of things works fine > (like the menu bar and so forth) - but the spreadsheet > display area is useless. > Is there any cure to this? > I have dealt with this a lot. The "cure" is somewhere in Redmond, but probably too low a priority for Microsoft. Sigh. The only workaround I know is to kill the excel process. -- Bob Gailer 510-978-4454 _______________________________________________ Python-win32 mailing list Python-win32@python.org http://mail.python.org/mailman/listinfo/python-win32 _______________________________________________ Python-win32 mailing list Python-win32@python.org http://mail.python.org/mailman/listinfo/python-win32
