COMP: fix capitalization on teem install library name and ENH: add demo application that builds against a built or installed teem using cmake
BUG: use all caps for #define symbols for consistency with the rest of the source code
COMP: put dll in bin and optionally put lib in TEEM-X.Y subdir
COMP: fix installation path so that shared libraries are installed in the TEEM-1.10 directory
change from option to set for path
ENH: added support for building with VTK's zlib and PNG
STYLE: fix typo in name
fix uninitialized dummy variable (led to runtime error condition on windows debug builds)
TEST: one character change to test checkin permission
added options for pointing to the dll config headers for png and zlib built by vtk
COMP: added math lib linkage for executables to support solaris (and other unices)
fixed cross-platform math lib linking
added new source file
added explicit linkage to math lib
added the binary include directory to the include path for builds
For our PythonQt app (3D Slicer, slicer.org), we bundle the ctkPythonConsole, which is great for easy access to basically everything in the system. http://www.commontk.org/index.php/Documentation/ImageGallery#Scripting.2FPython But people have also set up so that you can connect to the same python environment from many IDEs: https://www.slicer.org/wiki/Documentation/Nightly/Extensions/DebuggingTools And there's also now a way to use the python environment from Jupyter https://discourse.slicer.org/t/jupyter-notebooks-are-now-usable-in-3d-slicer/3438...
What's the next step on your end - will you make a new set of generated_cpp files in svn? As you know we try to keep the patched fork in CTK as close to your version as possible. https://github.com/commontk/PythonQt Thanks again for the fix!
Oops, sorry - my mistake: I forgot to include the patch to PythonQtMethodInfo.cpp. With that it's working!
I rebuilt with the current svn trunk of PythonQt. The QSocketNotifier include in qtscript_masterinclude.h was not needed. Unfortunately the new wrappings don't work for me - the constructor exists but it's not callable with a python integer. Is there a way to cast a python integer to a qintptr? This is the error message: File "/Users/pieper/slicer4/latest/SlicerWeb/WebServer/WebServer.py", line 1841, in start self.notifier = qt.QSocketNotifier(self.socket.fileno(),qt.QSocketNotifier.Read) ValueError:...
I call it the result of fileno() on python socket object. The python docs say this is "a small integer".
Sounds good. I can try some experiments in our fork and send you the diffs.
Okay, I guess I figured it out - adding this <primitive-type name="qintptr"/> to the end of line 168 of typesystem_core.xml appears to fix the wrapping fpr the socket classes (not tested yet, but the generated code looks like what I expect. There are many other rejected functions in the log so maybe it would be good to make a pass through and add more types?
Thanks Florian. I was able to run the generator with this command: $ QTDIR=~/Qt/5.8/gcc_64/ ./pythonqt_generator $ grep QSocketNotifier *.log mjb_rejected_functions.log:QSocketNotifier::d_func mjb_rejected_functions.log:QSocketNotifier::QSocketNotifier qintptr mjb_rejected_functions.log:QSocketNotifier::socket qintptr It looks like qintptr is not in the type system? There are a bunch of other socket-related classes listed in the rejected function log.
Hi Florian - It is indeed strange - everything else I've tried seems work fine. Maybe I'm the only one who used QSocketNotifier from PythonQt. If you look at the generated code from 4.8 in [1] it has the constructors and all the methods while the while the ones for 5.0 [2] only three methods. So the class is not completely skipped but it is incomplete for some reason. I agree the Qt headers look essentially the same so I suppose something happened in the generator process. In my workaround I copy...
Hi - We are in the process of switching from Qt 4.8 to Qt 5.10 for our app and most things work fine, but I recently noticed that QSocketNotifier is not available. Error is: >>> qsn = qt.QSocketNotifier() Traceback (most recent call last): File "<console>", line 1, in <module> ValueError: No constructors available for QSocketNotifier I was able to manually work around this by copying over the generated code from the older Qt version (see diff in link below) but I wonder if anyone knows how to fix...
eintrag eclipselink.ddl-generation create-tables
* change pom.xml to SNAPSHOT
add releng, updatesite and feature
* change encoding to utf-8
* add config for kepler build
* update projects maven repository
* update maven build
* add poms ...
* add license information to feature
add maven pom, uncomment GreeceImageTest
copy/delete works, MinimalWebApplicationCdi bui...
rm classes and bin folder
add MinimalWebApplication7 with Maven pom
* update maven pom
* change jarsigner certificate
* mv jarsigner to plugins
* add jarsigner plugin
properties in pom.xml einlesen
* add product pom
* set appname in builder
* get Eclipse from master
* update jacoco
* add xdoc and website generator
* Version Bump to 1.1.8
* update website
* add favicon.ico
* use new signing plugin
* add Features
* rename Preferences Page from Dsl to JEE6 Gen...
* rename website project
* add help plugin
* remove jboss banner
* remove juno, add luna
* fix zip ending
* update website
* prepare for update site
* add jee32.gif to bin.includes
* change updatesite facade
* update eclipse version for distro
* add doc plugin to feature
* update index.html
* update updatesite pom
* add plugin.xml to build.properties
* update update-site
* build distros for all Platforms
* add aboutus
* update utils to 1.1.9-SNAPSHOT
* Add version names
* set fqn for macbuilds
* configure signer from pom
* neu
* remove unused css files from old template
* Druckvorschau eingerichtet
* Drucklayout verbessert,
* yakindu.com links nutzen nun die bilder lokal
* delete images from xtext website
* Downloadseite und Generator angepasst
* fix releng link
* Move Distro build
* deutsches Impressum
* delete unused images
* Farben auf der Download seite von Rot auf Blau
* Update OAWTools
* entry-Methode im FAQ entfernt
* fix typo
* update design
* add css
* add logos
* delete generated files
* Bilder und Fonts aus dem alten Design entfernt
* neue Button
* add javascript
* revert
* unnötige Styleanweisungen aus dem HTML entfernt
* Update OAWtools