molodiuc / pythonxy

Automatically exported from code.google.com/p/pythonxy
0 stars 0 forks source link

Qwt plugins in QtDesigner are absent by default #244

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
Hi Everyone. I've installed Python(x,y) 2.6.6.0, in windows XP SP3 (32-bit) and 
7 64-bit.

The problem is simple, and shows up on both installs: In the QtDesigner bundled 
with Python(x,y), the widgets for Qwt are absent. A check in "About plugins..." 
reveals:

Failed plugins:
Cannot load library: 
C:\Python26\Lib\site-packages\PyQt4\plugins\designer\qwt_designer_plugin5.dll: 
Unable to the specified module

But qwt_designer_plugin5.dll does exist at the indicated path. Looking around 
the Internet I learned qwt_designer_plugin5.dll invokes qwt5.dll, which is 
generated by the compilation of Qwt from sources, but I didn't find the file 
anywhere within the pythonxy or Python26 folder trees. It would seem to me this 
file is not packaged in the installer. I think it is necessary to include it, 
in order to provide a full and convenient PyQwt design workflow.

Details of my installations:
I've selected all of the plugins save the medical ones, in case it helps. The 
directories I've chosen are:
- For Python 2.6 itself, the default (i.e. C:\Python26)
- For python(x,y), C:\data\progs\pythonxy
-  All subsequent content (docs, examples, etc.) are also placed under this 
folder.
I think I've installed for "Current user only". Before installing, I cleaned my 
computer from any previous Python installs, by running their uninstallers, 
manually removing leftover folders and running CCleaner to purge the registry. 

Original issue reported on code.google.com by macgyver...@gmail.com on 28 Apr 2011 at 11:21

GoogleCodeExporter commented 9 years ago
I've mistyped the error message. It is as follows:
Failed plugins:
Cannot load library: 
C:\Python26\Lib\site-packages\PyQt4\plugins\designer\qwt_designer_plugin5.dll: 
The specified module could not be found.

Thanks.

Original comment by macgyver...@gmail.com on 28 Apr 2011 at 11:22

GoogleCodeExporter commented 9 years ago
Typically this is caused by having some older Qt DLLs in the path.

If still applicable, please check the above and re-open the issue.

Original comment by grizzly.nyo on 23 Mar 2012 at 1:05