|
From: SourceForge.net <no...@so...> - 2012-06-05 13:34:30
|
Feature Requests item #3532135, was opened at 2012-06-05 05:33 Message generated for change (Comment added) made by mhammond You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=551957&aid=3532135&group_id=78018 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: pythonwin Group: None >Status: Closed >Resolution: Invalid Priority: 5 Private: No Submitted By: alt3rn1ty (alt3rn1ty) Assigned to: Nobody/Anonymous (nobody) Summary: Installer Finish page hidden by fullscreen Win 7 Initial Comment: Having a few issues with pywin32 217 for python 2.7.2 Downloading and launching your installer from an NSI installer (as prerequisites for a python based app) as noted here [url=http://forums.bethsoft.com/topic/1378796-rel-wrye-bash/page__view__findpost__p__20884125]Wrye Bash development topic[/url] Noticed by a few users on Win 7 around the various modding bazaars, when Pywin32 finishes installing, the finish page does not pop to front, leaving the user with a blank fullscreen blue Pywin32 background. [url=http://www.bild.me/bild.php?file=5033847Untitled2.jpg]screenshot[/url] Click once with the mouse and the installer dialogue will pop to front in focus presenting the user with a finish button to complete the installation. If window focus is un-achievable - Would it be possible to suppress fullscreen on the installer ?, or better still have an MSI instead of EXE ---------------------------------------------------------------------- >Comment By: Mark Hammond (mhammond) Date: 2012-06-05 06:34 Message: Not sure what an NSI installer is. Re the full-screen thing, I'm afraid this is a problem with bdist_wininst in distutils - part of Python itself - it needs to be fixed there. No .msi as bdist_msi doesn't have post-install scripts. It sounds like you are "bundling" Python with your app via individual setup apps - my advice is simply "don't do that" :) People could uninstall various parts and break you - things are generally out of your control. You should create a build process that gets the bits into a self-contained directory you then install as a unit. But either way, you could open the full-screen bug in the python.org tracker (add @mhammond to the nosy list if you do) - the .msi bug already exists. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=551957&aid=3532135&group_id=78018 |
