[PyKDE] Re: newest Version

Roland Schulz mail at r2s2.de
Fri Oct 31 14:59:01 GMT 2003

Hash: SHA1

I think the proxy idea won't work.
I haven't looked at the source enough before I wrote the proxy :-(. The 
problem is that QWidget,QObject and QPaintDevice all have a couple of friend 
classes. So I would need to proxy also all the private functions and I don't 
know wether they also access private variables. This will get to large to 
handle (at least for me).
So I'll try to do it in the sip layer. I don't think that this problem is 
(enterily) designer specific. It is a QMetaObject problem and this could be 
used by other C++ as well.
My first question about sip is: If I change some code in the PyQt sip files, 
how can I quickly rebuild PyQt. build.py takes so long because of all those 

On Friday 31 October 2003 08:57, Jim Bublitz wrote:
> On Thursday October 30 2003 22:52, Roland Schulz wrote:
> > On Thursday 30 October 2003 19:49, Jim Bublitz wrote:
> > > My suggestion (v2.0) would be to create (in C++) a proxy for
> > > QWidget (greatly oversimplified):
> >
> > currently the proxy idea is a step back. I have implemented
> > the proxy (see attachement). One can still place the Custom
> > Widget on a dialog and it is even rendered, but one can't
> > select it anymore. May be it is a easy problem - may be not. I
> > will try to find it out. But may be someone has time to look
> > at it too ;-))
> I've only taken a look at the code in the tarball (and pretty
> quickly too). The only thing I'd question is having className()
> always return "QWidget". I'm not sure if QtDesigner uses
> className for anything though, but that might be something to
> look at.
I'm just trying to get it working as good as without proxy. Before it returned 
QWidget so the proxy is also returning QWidget. This has to be changed but it 
is not what worries me right now.

Version: GnuPG v1.2.2-rc1-SuSE (GNU/Linux)


More information about the PyQt mailing list