[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-bindings
Subject:    Re: [Kde-bindings] Hacking moc-generated code
From:       Eric Jardim <ericjardim () gmail ! com>
Date:       2005-08-31 6:28:37
Message-ID: 432ec6c505083023284509b67c () mail ! gmail ! com
[Download RAW message or body]

[Attachment #2 (multipart/alternative)]


2005/8/31, Ashley Winters <jahqueel@yahoo.com>:
> 
> Here's how I would document Qt4's qt_metacall:
> 

Thanks, sooooo, much Ashley :)

I am starting to think that playing with qt_metacall will solve all of my 
python-qt4 problems. Instead of defining "signals" as protected functions, I 
can redirect it to Python methods. I just have to create a dynamic (not 
static) QMetaObject for each instace o Python extended QObject. That's the 
main difference betwee C++ and Python implementations of Qt.

I am only worried about if this is portable across platforms. But I think it 
is. There is not mystery in QMetaObject class. It is just a boilerplate 
code. The "party" goes inside those private (pimpl) classes of Qt.

Let's see what I can do with it! Now I'll create a pymoc script :)

Thanks, again...

[Eric Jardim]

[Attachment #5 (text/html)]

2005/8/31, Ashley Winters &lt;<a \
href="mailto:jahqueel@yahoo.com">jahqueel@yahoo.com</a>&gt;:<div><span \
class="gmail_quote"></span><blockquote class="gmail_quote" style="border-left: 1px \
solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"> Here's how \
I would document Qt4's qt_metacall:<br></blockquote></div><br> Thanks, sooooo, much \
Ashley :)<br> <br>
I am starting to think that playing with qt_metacall will solve all of
my python-qt4 problems. Instead of defining &quot;signals&quot; as protected
functions, I can redirect it to Python methods. I just have to create a
dynamic (not static) QMetaObject for each instace o Python extended
QObject. That's the main difference betwee C++ and Python
implementations of Qt.<br>
<br>
I am only worried about if this is portable across platforms. But I
think it is. There is not mystery in QMetaObject class. It is just a
boilerplate code. The &quot;party&quot; goes inside those private (pimpl) classes
of Qt.<br>
<br>
Let's see what I can do with it! Now I'll create a pymoc script :)<br>
<br>
Thanks, again...<br>
<br>
[Eric Jardim]<br>



_______________________________________________
Kde-bindings mailing list
Kde-bindings@kde.org
https://mail.kde.org/mailman/listinfo/kde-bindings


[prev in list] [next in list] [prev in thread] [next in thread]