[PyKDE] QObject::connectNotify
Hi - Is there a version of QObject::connectNotify for python signals, or a similar mechanism? I have a signal whose conditions are very expensive to calculate, so it would be better to not calculate its conditions if it is not connected. Thanks Jeremy ___ PyKDE mailing listPyKDE@mats.imk.fraunhofer.de http://mats.imk.fraunhofer.de/mailman/listinfo/pykde
[PyKDE] latest eric3 snapshot rocks!
Hi, just got around testing the latest snapshot - great! The toolbar-search is close to what I always dreamt of. Only a few questions arose: - it's a combo-box - but for me, it doesn't do anything. - is it possible to bind the incremental search to some key? - same for search next/prev incremental. I looked in the shortcuts, but no luck. Maybe I missed it - it's pretty crowded in there by now. And some semantics of the emacs incremental search I really like, so maybe they are feasible, too: 1) If one presses C-s, the minibuffer opens, and one can start typing. The equivalent here would be that the first press would put the focus into the search field 2) if C-s is pressed again while in the minibuffer, the search next functionality is executed - thus, no shortcut is wasted. So if the focus is in the search field, pressing the same shortcut would search again. 3) Pressing C-w while searching will expand the search term to the word-boundary the cursor is currently over. I better explain this by example: Let's say you have a few methods called show_*, where * is of course something like tables or images or whatever. Now when I want to find one of these, e.g. show_tables, I type C-s, then type show_. I then repeat pressing C-s. Of course all strings containing show_ are found. Now when the cursor is positioned over something like self.show_^tables with ^ indicating the cursor position. I can press C-w, which will expand the search term to the next word boundary - in this case show_tables. So I only search for that subsequently. 4) Pressing C-s twice when not in the minibuffer (or, so to speak, once again with an empty buffer, as the first puts the focus there) will reuse the last search term. I don't know if and which of these things is easy to implement - I guess having at least the possibility of shortcuts for search next/prev shouldn't be too hard. All other stuff is just a suggestion. All in all, it's always impressing at which speed eric evolves and how useful for me it becomes - so far it's the only IDE that lured me away from XEmacs, and that includes TogetherJ and Eclipse as failing competitors... Regards, Diez ___ PyKDE mailing listPyKDE@mats.imk.fraunhofer.de http://mats.imk.fraunhofer.de/mailman/listinfo/pykde
Re: [PyKDE] Request for Testing
Phil Thompson [EMAIL PROTECTED] wrote: Eventually produced... :) Attached to this mail. Followup: it could be reduced a little bit more. Attached again. Should be fixed in tonight's SIP snapshot - no need to rebuild PyQt. Thanks, works for my application. FYI, I will be out for a week or so since tomorrow, so I might be a little slow at testing further changes. -- Giovanni Bajo ___ PyKDE mailing listPyKDE@mats.imk.fraunhofer.de http://mats.imk.fraunhofer.de/mailman/listinfo/pykde
[PyKDE] invalid type for QSizePolicy()
Hi all, I recently installed Kubuntu and I'm facing some problems when I try to run one of my pyqt projects, which I started on a Fedora distro. When I try to run it, the following error occurs: TypeError: argument 1 of QSizePolicy() has an invalid type. I am aware that this error has been discussed here before, but I can't seem to solve the problem. I'm using Qt 3.3.3, KDE 3.4.0 and pyuic 3.13 for Qt version 3.3.3. I tried to regenerate the py file using pyuic but it didn't solve. In fact, I started a dummy application from scratch to see if the problem was in some weirdness in my .ui, but it wasn't. Can anyone give me a hint on how to solve this? I googled around and found a web site for some random app which says that the solution is to comment the lines which are causing the errors. Of course I can't do that :-) Thanks in advance, Bruno ___ PyKDE mailing listPyKDE@mats.imk.fraunhofer.de http://mats.imk.fraunhofer.de/mailman/listinfo/pykde
RE: [PyKDE] Request for Testing
My thanks as well, I can confirm that both the 8/21 and 8/22 snapshots work well for our application. I didn't have a chance to run extensive tests for memory leaks though. -Selim Selim Tuvi, Research Engineering Group, SLAC GLAST, IT Online, MS 98 Tel:650-926-3376 Fax:650-926-4335 -Original Message- From: [EMAIL PROTECTED] [mailto:pykde- [EMAIL PROTECTED] On Behalf Of Giovanni Bajo Sent: Tuesday, August 23, 2005 5:33 AM To: Phil Thompson Cc: pykde@mats.imk.fraunhofer.de Subject: Re: [PyKDE] Request for Testing Phil Thompson [EMAIL PROTECTED] wrote: Eventually produced... :) Attached to this mail. Followup: it could be reduced a little bit more. Attached again. Should be fixed in tonight's SIP snapshot - no need to rebuild PyQt. Thanks, works for my application. FYI, I will be out for a week or so since tomorrow, so I might be a little slow at testing further changes. -- Giovanni Bajo ___ PyKDE mailing listPyKDE@mats.imk.fraunhofer.de http://mats.imk.fraunhofer.de/mailman/listinfo/pykde ___ PyKDE mailing listPyKDE@mats.imk.fraunhofer.de http://mats.imk.fraunhofer.de/mailman/listinfo/pykde
