Language Bindings

thanks a lot for this, nice posting, i think you should carry on.

looks promising, thanks for the heads up.

Sorry but I have edited your edit a little :)

I changed "Windows (32bits):" to "Windows:" ... it is ok Windows to be 64 bit (mine is).

The (partial) solution was this:

@self.group.setHandlesChildEvents(False) @

This ensures that individual items handle their own events, it seems that before the group was capturing them.

I still have a problem in that my GraphicsView overrides the mouseMoveEvent, and when enabled, no events get propagated to scene items.

Woops, I found the reason by myself...

@class myClass(anotherLib.originalClass, QtCore.QObject):
def init(self,username,password):
QtCore.QObject.init(self)@

Adding the QObject parent class and calling it during the init

[quote author="pmcfrack" date="1300306178"]I know this is a rather old post, however, this is the exact problem I am trying to work around. Here is a link to my question: http://developer.qt.nokia.com/forums/viewthread/4402/#26159

Does anyone have a work around for this?

Thanks![/quote]

Perhaps you should start responding in that thread then again? It is not like you did not get any reactions there...

This QtWui looks like stuff you build on server and then you use it with normal browser? I don’t really get the benefit of this framework... Or is it something like Rails? Its website doesn’t really tell.

OTOH Jambi is Qt bindings for Java. But because it is Java, it should be possible to use Jambi in applets and JNLP stuff. If you are just wanting to write something for web server, you’re most likely better off with Qt/cpp, since you already know it.

As far as I know, pyside only work with python 2.* versions
*Could be mistaken.

:)

[quote]That's why editing headers is difficult :-)[/quote]

Oey, In the back of my mind I was thinking the same thing.

Aside from a custom widget (have yet to figure out painting),
editing works if passing header information into an external dialog.

Not exactly what I intended for the user, but it works :)

Thank you for your kind help.

The 64bit packages are ready for testing.
"https://launchpad.net/~qtjambi-community/+archive/libqtjambi/+packages":https://launchpad.net/~qtjambi-community/+archive/libqtjambi/+packages

Great work! I'm looking forward for the final release!

However, as the project is sponsored by Nokia, to provide Python support for mobile phones (I read it somewhere on the project's website), will there be any repercussion on the project? (Reference to http://blog.qt.nokia.com/2011/02/14/update-on-qt/, for example.) I didn't read anything about it...

The last release was at January 21th, this new yesterday juts 13 days after, because our "sprint " is in the end and we fixed the planned bugs faster than we thought, and all task as done 2 days earlier. :D

Working hard to get 1.0.0 ASAP. :D

Thanks, it worked! I was using img.tostring() (from OpenCV), that is why I didn't think that it is going to be garbage collected and I didn't suspect that Qt is so smart to use the same memory instead of allocating and copying. Thanks again!

The problem was caused by 64bit Python installation.
Using 32bit Python solved the problem.