[issue5019] Specifying common controls DLL in manifest

Robin Dunn added the comment: Update: I finally worked out what needed to be done for wxPython and while simply changing Python's manifest would have been immensely easier what I have does seem to work well so I thought I should give some info here for posterity. I went back and experimented a

[issue5019] Specifying common controls DLL in manifest

Robin Dunn added the comment: Thanks for the code. I've verified your findings and I've also converted nested to an extension module and built it with distutils and was still able to make it correctly load the themed common controls when imported from Python, however I had to hack distutils a l

[issue5019] Specifying common controls DLL in manifest

Martin v. Löwis added the comment: Here is a demo of how to make a nested DLL bind to comctl32 v6, even if the main application binds to a different version of comctl. The DLL has a ISOLATIONAWARE_MANIFEST_RESOURCE_ID resource. To see what happens, run Release\bindtest.exe, and invoke File/test

[issue5019] Specifying common controls DLL in manifest

Robin Dunn added the comment: Sorry, no luck. I've tried before to ensure that all the DLLs and extension modules have the manifest file (in resource 2) and it makes no difference. I rebuilt wxWidgets and wxPython today with ISOLATION_AWARE_ENABLED defined to check if that would help, and rese

[issue5019] Specifying common controls DLL in manifest

Martin v. Löwis added the comment: It looks like it should be possible to bind to a different comctl32.dll than what gets loaded by the host application. See this KB article: http://support.microsoft.com/default.aspx/kb/830033 which even claims that you should be able to do so with manifests (

[issue5019] Specifying common controls DLL in manifest

Changes by Robin Dunn : Added file: http://bugs.python.org/file12997/Snap001.png ___ Python tracker ___ ___ Python-bugs-list mailing list Unsub

[issue5019] Specifying common controls DLL in manifest

Changes by Robin Dunn : Added file: http://bugs.python.org/file12998/Snap002.png ___ Python tracker ___ ___ Python-bugs-list mailing list Unsub

[issue5019] Specifying common controls DLL in manifest

Changes by Robin Dunn : Added file: http://bugs.python.org/file12996/sample.py ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubsc

[issue5019] Specifying common controls DLL in manifest

Robin Dunn added the comment: Ok, the following files will be attached: python.exe.manifest: This is a copy of the manifest resource that I put into the 2.6.1 python.exe file by hand for testing. The original manifest was the same but without the 2nd ... group. sample.py: the simple little sa

[issue5019] Specifying common controls DLL in manifest

Martin v. Löwis added the comment: Can you provide an example of a manifest file, and a Python script, that demonstrates the problem? I have only heard of themes, never seen them myself. ___ Python tracker _

[issue5019] Specifying common controls DLL in manifest

Robin Dunn added the comment: If I understand correctly then setting an activation context won't help because by the time that an extension module is loaded the choice of which version of the common controls DLL will be loaded has already been made, and it may in fact already be loaded. The sys

[issue5019] Specifying common controls DLL in manifest

Martin v. Löwis added the comment: See issue4566. If you explicitly create "activation contexts", you might be able to have it load the right DLLs. -- nosy: +loewis ___ Python tracker __

[issue5019] Specifying common controls DLL in manifest

New submission from Robin Dunn : This may have already been discussed but my searches didn't turn up anything concrete other than issue 4120 which is a similar but different problem. The problem I'm facing is that wxPython requires that version 6 of the common controls DLL be loaded in order for