Re: [PyKDE] import libqtc : module not found error! : Newbie
On Fri, 14 Dec 2001, karthik Guru wrote: [...] > ImportError: DLL load failed: The specified module could not be found. The Windows non-commercial QT version doesn't place the Qt-dll into the appropriate directory, which is for your version the /system32. Solution is simple: Take the /bin/qt-mt230nc.dll and copy it into /system32. Cheers, :M: ___ PyKDE mailing list[EMAIL PROTECTED] http://mats.gmd.de/mailman/listinfo/pykde
[PyKDE] setUpdatesEnabled
Hi, I have the feeling setUpdatesEnabled don't work for me. I have a database with several hundred entries which are inserted in a QTable. I want to forbid repaints during the insertion process, so I call QTable.setUpdatesEnabled(0) However, it is still repainting. What am I missing? Yours, :M: -- || | Dipl.-Inf. Michael 'Mickey' Lauer[EMAIL PROTECTED] | | Raum 10b - ++49 69 798 28358Fachbereich Informatik und Biologie | || ___ PyKDE mailing list[EMAIL PROTECTED] http://mats.gmd.de/mailman/listinfo/pykde
Re: [PyKDE] setUpdatesEnabled
Ok, once again one should think before post. I guess it's clear to me now. Qt's policy on forbidding updates is not to automagically include child widgets. I use QTable.hide() and QTable.show() now, which does the job. Happy new year, by the way :) :M: -- || | Dipl.-Inf. Michael 'Mickey' Lauer[EMAIL PROTECTED] | | Raum 10b - ++49 69 798 28358Fachbereich Informatik und Biologie | || ___ PyKDE mailing list[EMAIL PROTECTED] http://mats.gmd.de/mailman/listinfo/pykde
Re: [PyKDE] PyQt for Qt/Embedded
> > The rest of the users compile Qt/E on their own. During the ./configure > > step there is a selection between 5 preset configurations > > (unfortunately only named Minimal, Small, Standard, Large, All). > > Alternatively you can use your own config file and define what > > gets in via the compile-time definitions. > > The current CVS should now have enough features defined for the Large > configuration. I haven't added all the remaining features for smaller > configurations yet. This is GREAT! Thanks for your work. I will try to get PyQt on iPAQ running tomorrow. *crossing fingers* :) Yours, Michael Lauer. ___ PyKDE mailing list[EMAIL PROTECTED] http://mats.gmd.de/mailman/listinfo/pykde
[PyKDE] PyQt/Embedded on iPAQ
Hello, I just wanted to try out PyQt/E on iPAQ using the ipkg packages from Phil Thompson. Problem: I can't import qt. This is why: --- on ipaq --- >>> import qt Traceback (most recent call last): File "", line 1, in ? File "/tmp/arm-linux.20350/lib/python2.2/site-packages/qt.py", line 44, in ? ImportError: /usr/lib/libqte.so.2: undefined symbol: pnG_push_crc_finish --- Yo, welcome to the dynamic library hell... I guess libqte.so is trying to lookup this symbol from a PNG library... but wait: libqte is supposed to have the PNG included, isn't it? It seems the binary of the qte library in the ipaq familiar linux is not out of the box compatible with the qte library you used when compiling qte - which is a major problem for me... and which brings me to the important question: Phil, which qte library did you link against when compiling pyqte for the zaurus? On a (slightly related) side note: Does anyone know how to find out which compiler was used to compile a certain binary file? Did anyone manage to get a working PyQtE environment on the Compaq iPAQ yet? If so, how? I have just managed to get a working gcc environment on my iPAQ but I'm hesitating to compile all the stuff by hand... it would take ages... Yours, :M: -- || | Dipl.-Inf. Michael 'Mickey' Lauer[EMAIL PROTECTED] | | Raum 10b - ++49 69 798 28358Fachbereich Informatik und Biologie | || ___ PyKDE mailing list[EMAIL PROTECTED] http://mats.gmd.de/mailman/listinfo/pykde
[PyKDE] SUCCESS!!! (was: PyQt/Embedded on iPAQ)
Hi - just a small success note: Last week I wrote about a binary (symbol not found) problem using zaurus PyQt and Python ipkgs with the qpe/opie build: > Yo, welcome to the dynamic library hell... I guess libqte.so is trying > to lookup this symbol from a PNG library... but wait: libqte is supposed > to have the PNG included, isn't it? It seems the binary of the qte library > in the ipaq familiar linux is not out of the box compatible with the qte > library you used when compiling qte - which is a major problem for me now... The new OPIE build from Biplolar contains a new version of qt-embedded (using the built in libpng), which is compatible with Phil Thompsons PyQt ipkg's. I hope the binary compatiblity stays for a few releases :) We can now program Qtopia applications in Python - yahoo! Thanks to all who were involved (especially Phil Thompson, Bipolar and all the Trolltech and Python guys). Yours, Mickey. ___ PyKDE mailing list[EMAIL PROTECTED] http://mats.gmd.de/mailman/listinfo/pykde
Re: [PyKDE] PyQt on Win2000
Am Don, 2002-04-11 um 02.09 schrieb Roundy, Lance: > I'm interested in trying PyQt out. I've installed the Non-Commercial > version of Qt as well as the associated PyQt module. All the installs > seemed to go fine. However my initial attempt to import qt results in... > > >>> from qt import * > Traceback (most recent call last): > File "", line 1, in ? > from qt import * > File "D:\Program Files\Python22\lib\qt.py", line 46, in ? > import libsip > ImportError: DLL load failed: The specified module could not be found. > > >From what I read PyQt included the SIP module but all I can find on my > system is libsip.dll under the Python 2.2 libs directory. copy libsip.dll to /system32 -- :M: -- || | Dipl.-Inf. Michael 'Mickey' Lauer [EMAIL PROTECTED] | | Raum 10b - ++49 69 798 28358Fachbereich Informatik und Biologie | || ___ PyKDE mailing list[EMAIL PROTECTED] http://mats.gmd.de/mailman/listinfo/pykde
Re: [PyKDE] what do I need to develop qpe-Applications using PyQt?
Am Mon, 2002-05-27 um 09.33 schrieb Phil Thompson: > One obvious problem (probably not this one) is that the Zaurus uses Qt > 2.3, not Qt 3. Exactly. And while qt-embedded 3.1 as well as qtopia-3 (using qt-embedded 3.1) is shaping up nicely, it will take quite some additional time for it to finalize, let alone to have it included in the zaurus or ipaq roms. Yours, -- :M: -- || | Dipl.-Inf. Michael 'Mickey' Lauer [EMAIL PROTECTED] | | Raum 10b - ++49 69 798 28358Fachbereich Informatik und Biologie | || ___ PyKDE mailing list[EMAIL PROTECTED] http://mats.gmd.de/mailman/listinfo/pykde
[PyKDE] PyQt on iPAQ / PyQt on OpenZaurus
FYI: Recent modifications by sharp or trolltech broke PyQt compatibility with the iPAQ and Zaurus running Familiar/Opie respectively OpenZaurus. I've submitted a patch to opie-cvs which got its way in and now PyQt runs again on Familiar/Opie and OpenZaurus. Yours, :M: -- || | Dipl.-Inf. Michael 'Mickey' Lauer[EMAIL PROTECTED] | | Raum 10b - ++49 69 798 28358Fachbereich Informatik und Biologie | || ___ PyKDE mailing list[EMAIL PROTECTED] http://mats.gmd.de/mailman/listinfo/pykde
RE: [PyKDE] PyKDE and libkdegames
Am Mon, 2002-06-10 um 18.53 schrieb Jim Bublitz: > I have some semi-automated tools to do it, > but they only generate about 80% - 90% clean code and require a lot > of manual touch-up. Sounds very interesting - could you publish these tools, please? Yours, :M: ___ PyKDE mailing list[EMAIL PROTECTED] http://mats.gmd.de/mailman/listinfo/pykde
Re: [PyKDE] PyKDE and libkdegames
Am Don, 2002-06-13 um 20.47 schrieb Ricardo Javier Cardenes Medina: > On Thu, Jun 13, 2002 at 09:46:26AM -0700, Jim Bublitz wrote: > > At the moment I simply don't have the time to work on this or > > co-ordinate a project, but I'll be happy to answer any questions. > > > > If anyone is interested, let me know. > > I'd like to see that :-) Me, too! :) ___ PyKDE mailing list[EMAIL PROTECTED] http://mats.gmd.de/mailman/listinfo/pykde
Re: [PyKDE] pyuic patch for use with designer 3
Am Mon, 2002-06-17 um 18.15 schrieb Christian Bird: > Hello all, > > I've been using PyQt and qt designer 3 quite a lot lately and was a bit bummed > that I couldn't use the integrated source editor when creating slots > connected to signals for various widgets. To overcome this, I hacked a bit > on pyuic so that it will include the code from various functions defined in > foo.ui.h when creating a python class from foo.ui. I don't know if this will > be helpful at all for others, but it's helped me a lot. I found this to be very helpful! Thanks a lot. > To use it, apply the patch to PyQt-3.2.4/pyuic/form.cpp Could it be integrated into the main distribution, Phil? -- :M: -- || | Dipl.-Inf. Michael 'Mickey' Lauer [EMAIL PROTECTED] | | Raum 10b - ++49 69 798 28358Fachbereich Informatik und Biologie | || ___ PyKDE mailing list[EMAIL PROTECTED] http://mats.gmd.de/mailman/listinfo/pykde
[PyKDE] qwidgetstack.sip bug
Hi, - %If (- Qt_3_0_0) void addWidget(QWidget * /Transfer/,int); %End %If (Qt_3_0_0 -) void addWidget(QWidget * /Transfer/,int = -1); %End - is wrong. It should be - %If (- Qt_3_0_0) void addWidget(QWidget * /Transfer/,int); %End %If (Qt_3_0_0 -) int addWidget(QWidget * /Transfer/,int = -1); %End - Yours, -- :M: -- Dipl.-Inf. Michael 'Mickey' Lauer [EMAIL PROTECTED] Raum 10b - ++49 69 798 28358 Fachbereich Informatik und Biologie -- ___ PyKDE mailing list[EMAIL PROTECTED] http://mats.gmd.de/mailman/listinfo/pykde
[PyKDE] Qt shutting down the process/Python interpreter - necessary?
Hi,
in Qt there are certain places, where exit() is called, for instance,
if you construct a QPaintDevice before a QApplication, the process ends.
This behaviour - while perhaps being reasonable in a compiled language -
seems truly inappropriate in the context of an interpretated interactive
and dynamic environment such as the Python interpreter.
It would be much more useful if this would raise an exception, like,
PyQtException, which we could catch and react appropriate - for
instance, generating the application object and trying again.
It's especially bugging me in Qt/Embedded, where the offending exit()
call is triggered, when you create a QApplication in client mode but
no QWS server is running. It would be sufficient to just recreate the
QApplication with the appropriate parameter (-qws), but I can't because
my interpreter is being shutdown [see below] :(
mickey@gandalf:~/work/elan$ python
Python 2.2.2 (#1, Oct 27 2002, 17:30:06)
[GCC 3.2 (Mandrake Linux 9.0 3.2-1mdk)] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> import qtpe
>>> try:
... a=qtpe.QApplication([])
... except:
... pass
...
QSocket::writeBlock: Socket is not open
QSocket::writeBlock: Socket is not open
QSocket::writeBlock: Socket is not open
No Qt/Embedded server appears to be running.
If you want to run this program as a server,
add the "-qws" command-line option.
mickey@gandalf:~/work/elan$
This behaviour is due to the following code:
void QWSDisplayData::waitForConnection()
{
#ifndef QT_NO_QWS_MULTIPROCESS
for ( int i = 0; i < 5; i++ ) {
if ( csocket ) {
csocket->flush();
csocket->waitForMore(2000);
}
fillQueue();
if ( connected_event )
return;
usleep( 5 );
}
#else
if ( connected_event )
return;
#endif
qWarning("No Qt/Embedded server appears to be running.");
qWarning("If you want to run this program as a server,");
qWarning("add the \"-qws\" command-line option.");
exit(1);
}
Now, my question... is there something I can do at python level
or is there something we can do at PyQt level to change this behaviour?
Yours,
--
:M:
--
Dipl.-Inf. Michael 'Mickey' Lauer
[EMAIL PROTECTED]
Raum 10b - ++49 69 798 28358 Fachbereich Informatik und Biologie
--
___
PyKDE mailing list[EMAIL PROTECTED]
http://mats.gmd.de/mailman/listinfo/pykde
Re: [PyKDE] PyQt Support for Qt 3.1.0
Am Mon, 2002-11-11 um 14.09 schrieb Phil Thompson: > The current PyQt snapshots now have full support for Qt 3.1.0. > > The only area where the changes might cause problems is pyuic - please test if > you are a heavy pyuic user (even if you are not using Qt 3.1.0). > > Please consider snapshots from now on as release candidates for PyQt 3.5. Could you please review and integrate the qtpe additions from David Douard for PyQt 3.5 Yours, -- :M: -- Dipl.-Inf. Michael 'Mickey' Lauer [EMAIL PROTECTED] Raum 10b - ++49 69 798 28358 Fachbereich Informatik und Biologie -- ___ PyKDE mailing list[EMAIL PROTECTED] http://mats.gmd.de/mailman/listinfo/pykde
[PyKDE] qApp - myApp relationship
Hi, some question concerning the relationship between the qt module global qApp attribute and the actual QApplication-derived object which I instanciate? Why is there a qApp object directly after importing the qt module? Is it safe and wise to rebind the qApp with my customized QApplication instance? Yours, ___ PyKDE mailing list[EMAIL PROTECTED] http://mats.gmd.de/mailman/listinfo/pykde
Re: [PyKDE] QTable, selections and moving column headers
Am Mit, 2002-11-20 um 00.22 schrieb greg Landrum: > > [PyQt-3.3.2, qt-3.0.5, RH8.0, Python-2.2.1] > > The attached file constructs a simple widget using a QTable. > It also attempts to: > 1) limit selection to a single cell > 2) allow moving of columns and rows > as near as I can tell, neither 1) nor 2) work. Hmm... works fine here. You do know that you must press CTRL while moving columns and rows, do you? :-) Cheers, -- :M: -- Dipl.-Inf. Michael 'Mickey' Lauer [EMAIL PROTECTED] Raum 10b - ++49 69 798 28358 Fachbereich Informatik und Biologie -- ___ PyKDE mailing list[EMAIL PROTECTED] http://mats.gmd.de/mailman/listinfo/pykde
Re: [PyKDE] QTable, selections and moving column headers
Hi Greg, > > Hmm... works fine here. > > You do know that you must press CTRL while moving columns and rows, do > > you? :-) > > No, that I did not know, but you are right. Do you know if this > "feature" is actually documented anywhere? Hehe... no - actually I must confess that I found it out by accident :) No idea how to change this behaviour... seems to be implemented in the private QTable section. Yours, -- :M: -- Dipl.-Inf. Michael 'Mickey' Lauer [EMAIL PROTECTED] Raum 10b - ++49 69 798 28358 Fachbereich Informatik und Biologie -- ___ PyKDE mailing list[EMAIL PROTECTED] http://mats.gmd.de/mailman/listinfo/pykde
Re: [PyKDE] Speed of derived objects
Am Son, 2002-11-24 um 23.35 schrieb Vincent Wagelaar: > I am currently working with a QListView and QListViewItem. If I don't derive > from these objects speed is great, but derived these objects become very > slow. First of all - you are experiencing an inherent fact in the nature of Python bindings which support deriving and virtual methods. If you don't subclass, there's nearly no Python code involved - if you do subclass, your (really really slow - compared to the speed of executing code in C/C++ extension modules) Python code is called. There's nothing you can do about this fact. >What is the usual approach for speeding this up? You have to be very careful about _what_ methods you overload. For instance, overloading event() is a very bad idea, because event() is called very often - hence slow Python code gets executed very often. Also, try implementing behaviour using C++-SIGNALS wherever it is possible. You might want to check if removing your additional debugging code (print statements are known to slow down very much) makes a difference, too. If this all don't work for you, then I'm afraid you have to implement your derived class in C++ and use sip to bind this and use it from Python. Yours, Mickey. -- :M: -- Dipl.-Inf. Michael 'Mickey' Lauer [EMAIL PROTECTED] Raum 10b - ++49 69 798 28358 Fachbereich Informatik und Biologie -- ___ PyKDE mailing list[EMAIL PROTECTED] http://mats.gmd.de/mailman/listinfo/pykde
Re: [PyKDE] Dialog ignoring Mode flag
Am Fre, 2002-11-29 um 15.05 schrieb George Moody: > Using this simple dialog (shown below), I am unable to get it to display in > modeless form, irrespective of how the modal value is set in the Qdialog > creation. A modeless dialog has to be show()'n, not exec_loop'ed :) Cheers, Mickey. -- :M: -- Dipl.-Inf. Michael 'Mickey' Lauer [EMAIL PROTECTED] Raum 10b - ++49 69 798 28358 Fachbereich Informatik und Biologie -- ___ PyKDE mailing list[EMAIL PROTECTED] http://mats.gmd.de/mailman/listinfo/pykde
[PyKDE] Multithreaded GUI programming
Hi, I have a question regarding efficient programming in a multithreaded environment. Our scenario deals with Qt, but the problem is a general one. Our setup is a typical multithreaded one: We have a number of worker threads and one GUI thread, both communicating via a Queue. The problem is: How not to waste CPU resources by using a timer to poll the communication Queue from within the GUI thread. Some more information: Since we're targetting a PDA with Qt/Embedded, we're using PyQt. The PDA runs a non-threaded Qt/Embedded 2.3.4 and will for quite a long time. Qt/E 2.3.4 is _not_ thread-safe, so all calls to Qt must be done from same thread. This also means, it's unfortunately not possible to call QApplication.postEvent() from a worker thread to make the GUI thread to check for a new message in the Queue. How is this handled in low-level programs? In C++, I would use a pipe for the communication and would overload the main event loop adding a pipe file descriptor to the select() call. This way I can simultaneously wait for gui events and non-gui events without wasting CPU resources. In Python, the situation is different, since I can't overload the main loop - it would be much to slow (let alone, that the internal gui main loop functions are private and thus are not exported). Even if I could, in Python I'd rather use Queues than pipes - and a Queue is nothing which can just be added to a select call. Could you share some insights with me? Cheers, Mickey. -- :M: -- Dipl.-Inf. Michael 'Mickey' Lauer [EMAIL PROTECTED] Raum 10b - ++49 69 798 28358 Fachbereich Informatik und Biologie -- ___ PyKDE mailing list[EMAIL PROTECTED] http://mats.gmd.de/mailman/listinfo/pykde
Re: [PyKDE] Multithreaded GUI programming
> The problem is: How not to waste CPU > > resources by using a timer > > to poll the communication Queue from within the GUI thread. > > I don't imagine that the polling is going to be particularly expensive but > I've never measured it. Have you? We've done some tests -- not by measuring, but by evaluating the responsiveness. Basically, it depends on how frequently you poll. As I've said in another mail, handling a timerEvent in Python code is inherently _slow_, because interpreted code is being executed rather than compiled code. A timer set to - say - hundred milliseconds or less _will_ slow down the GUI event processing noticably, when handled in Python code. However, if the timer is set to, say seconds instead of milliseconds, the slowdown will be hardly noticable, but the latency, i.e. the time between the worker thread notifies the GUI and the GUI actually has a chance to poll the queue and to update the display, will increase. > Are you not able to use QApplication.lock() and unlock() around the postEvent? Unfortunately not. lock() and unlock() are only available in multithreaded Qt. Yours, -- :M: -- Dipl.-Inf. Michael 'Mickey' Lauer [EMAIL PROTECTED] Raum 10b - ++49 69 798 28358 Fachbereich Informatik und Biologie -- ___ PyKDE mailing list[EMAIL PROTECTED] http://mats.gmd.de/mailman/listinfo/pykde
Re: [PyKDE] Sharp Zaurus support
Hi Greg, > I'm considering putting together a PyQt based app for the Sharp Zaurus and > would like to know what kind of success people have had. Great success. We have a very large PyQt application on the Sharp Zaurus and despite some minor issues its working really good. > Is the Zaurus > version of PyQt based on Qt 3.x or on one of the Qt 2.x series? Qt/E 2.3.x > Is the > Zaurus version trimmed down in any way or do I get all the features that I > would have available to a desktop app? The Zaurus (as is the iPAQ) build of Qt/Embedded is a stripped down build, several features as following are missing: #define QT_NO_CODECS #define QT_NO_UNICODETABLES #define QT_NO_IMAGEIO_PPM #define QT_NO_FREETYPE #define QT_NO_BDF #define QT_NO_DRAGANDDROP #define QT_NO_PROPERTIES #define QT_NO_NETWORKPROTOCOL #define QT_NO_IMAGE_TEXT #define QT_NO_COLORNAMES #define QT_NO_TRANSFORMATIONS #define QT_NO_TRANSLATION_BUILDER #define QT_NO_COMPLEXTEXT #define QT_NO_PRINTER #define QT_NO_PICTURE #define QT_NO_DIAL #define QT_NO_SIZEGRIP #define QT_NO_WORKSPACE #define QT_NO_STYLE_POCKETPC #define QT_NO_STYLE_MOTIF #define QT_NO_STYLE_PLATINUM #define QT_NO_FILEDIALOG #define QT_NO_FONTDIALOG #define QT_NO_PRINTDIALOG #define QT_NO_COLORDIALOG #define QT_NO_INPUTDIALOG #define QT_NO_PROGRESSDIALOG #define QT_NO_WIZARD #define QT_NO_EFFECTS #define QT_NO_DOM #define QT_NO_SEMIMODAL #define QT_NO_SPLITTER #define QT_NO_QWS_BEOS_WM_STYLE #define QT_NO_QWS_KDE2_WM_STYLE Yours, -- :M: -- Dipl.-Inf. Michael 'Mickey' Lauer [EMAIL PROTECTED] Raum 10b - ++49 69 798 28358 Fachbereich Informatik und Biologie -- ___ PyKDE mailing list[EMAIL PROTECTED] http://mats.gmd.de/mailman/listinfo/pykde
Re: [PyKDE] Sharp Zaurus support
Am Don, 2002-12-12 um 16.48 schrieb Greg Fortune: > I assume I could recompile Qtopia to re-enable any of these features I need, > right? You can recompile Qt/Embedded with less disabled features, however you will lose binary compatibility with stock Zaurii, of course. If you really really need a missing feature then it would be better to refactor this feature into a seperate library and enhance the PyQt build process to support this. If you want to go this way, let's join forces - I'd be interested. Cheers, -- :M: -- Dipl.-Inf. Michael 'Mickey' Lauer [EMAIL PROTECTED] Raum 10b - ++49 69 798 28358 Fachbereich Informatik und Biologie -- ___ PyKDE mailing list[EMAIL PROTECTED] http://mats.gmd.de/mailman/listinfo/pykde
Re: [PyKDE] Sharp Zaurus support
Am Don, 2002-12-12 um 19.45 schrieb Greg Fortune: > > > > > > > I assume I could recompile Qtopia to re-enable any of these features I > > > need, right? > > > > You are confusing Qt/Embedded with Qtopia. I don't know if you can compile > > your own Qt/Embedded as it would require knowledge of the Zaurus hardware. > > > > Perhaps Sharp provides something like a makefile for their platform. Luckily this is not needed. Qt/Embedded comes with all the necessary configurations. Simply configure Qt/Embedded with ./configure -xplatform linux-sharp-g++ and you're set. Note that you need a cross compilation environment. Yours, -- :M: -- Dipl.-Inf. Michael 'Mickey' Lauer [EMAIL PROTECTED] Raum 10b - ++49 69 798 28358 Fachbereich Informatik und Biologie -- ___ PyKDE mailing list[EMAIL PROTECTED] http://mats.gmd.de/mailman/listinfo/pykde
Re: [PyKDE] ANN: SIP/PyQt v3.5 & QScintilla v0.3 Released
Phil, congratulations for this new release! I'm especially happy that the enhanced Qtopia support has made it into this release. One thing though (ya' know, some folks just can't get enough :)): Could you give me a hint how to wrap QCopEnvelope? I need it for our project since calling /opt/QtPalmtop/bin/qcop is way to slow. The issue came up on this list, once, and IIRC the problem was the support for the << operator which QCopEnvelope relies on. Would it be difficult to implement QCopEnvelope using a simple class method, e.g. QCopEnvelope.post instead of the << operator? Cheers and please keep up the great work. Yours, -- :M: -- Dipl.-Inf. Michael 'Mickey' Lauer [EMAIL PROTECTED] Raum 10b - ++49 69 798 28358 Fachbereich Informatik und Biologie -- ___ PyKDE mailing list[EMAIL PROTECTED] http://mats.gmd.de/mailman/listinfo/pykde
Re: [PyKDE] ANN: SIP/PyQt v3.5 & QScintilla v0.3 Released
Am Fre, 2002-12-13 um 02.11 schrieb Phil Thompson:
> > Could you give me a hint how to wrap QCopEnvelope? I need
> > it for our project since calling /opt/QtPalmtop/bin/qcop is way to slow.
[...]
I have wrapped QCopEnvelope with success.
> There shouldn't be any problem implementing the << operator by providing an
> __lshift__ method in the same way that __iadd__ is implemented for
> QSemaphore.
I overlooked that QCopEnvelope is derived from QDataStream. QDataStream
doesn't implement the << and >> operators, but provides writeBytes(),
which should be sufficient... if there wasn't a problem concerning the
data bytes.
One example: Sending a QCOP message without parameters works very good,
e.g. the following code make an hourglass appear on the taskbar
("del e" is neccessary, because the QCopEnvelope sends its message in
the C++ destructor):
e = qtpe.QCopEnvelope( "QPE/System", "busy()" )
del e
Very good. Sending a QCOP message with parameters also works fine, when
the receiver is PyQt, e.g.
e = qtpe.QCopEnvelope( "QPE/Application/elan", "message()" )
e.writeBytes( "HelloWorld!" )
del e
works also as expected.
Now the case which does not function: The following code _should_ make a
string appear on the TaskBar (it's basically the same what
Global::statusMessage() does):
e = qtpe.QCopEnvelope( "QPE/TaskBar", "message(QString)" )
e.writeBytes( "HelloWorld!" )
del e
But the only thing I get is garbage on the taskbar. The message seems to
be received, but somehow the data is not "marshalled" or interpretated
correctly. Or could it be possible (since the message is sent inside the
destructor) that the corresponding char* has been deleted or overwritten
before it is accessed by the QCopEnvelope?
Yours,
--
:M:
--
Dipl.-Inf. Michael 'Mickey' Lauer
[EMAIL PROTECTED]
Raum 10b - ++49 69 798 28358 Fachbereich Informatik und Biologie
--
___
PyKDE mailing list[EMAIL PROTECTED]
http://mats.gmd.de/mailman/listinfo/pykde
Solved [Re: [PyKDE] QPEApplication.setStylusOperation() woes]
Quoting my own message from 2002-08-29: > Dear fellow PyQt'ers... > > did anyone have luck using QPEApplication.setStylusOperation( > QPEApplication.RightOnHold)? It simply doesn't work for me: > no right press event is emitted when it should be. > > I'm currently patching a libqpe.so to print out some debug information, > maybe someone else can also shed some light onto this situation? Apparantly it has been a problem with timerEvent() in QPEApplication which was commented out in PyQt 3.4 (a fact I only recently stumbled over when I was diff'in 3.4 and 3.5 :-) As a workaround I wrote the complete stylus handling in python -- which worked fine. However, this is no longer necessary, because setStylusOperation (aka the timerEvent() in QPEApplication) finally works in PyQt 3.5. I don't know if you explicitly looked into this, Phil, but I'm glad that it is functional now :) Thanks, Mickey. ___ PyKDE mailing list[EMAIL PROTECTED] http://mats.gmd.de/mailman/listinfo/pykde
QCop Messages (was Re: [PyKDE] ANN: SIP/PyQt v3.5 & QScintilla v0.3Released)
Hi,
In order to further investigate why the taskbar is showing trash,
I did the following addition to TaskBar::receive():
void TaskBar::receive( const QCString &msg, const QByteArray &data )
{
int size = data.size();
qDebug( "TaskBar::receive - bytearray size %d", size );
for ( int i = 0; i < size; ++i )
qDebug( "TaskBar::receive - byte %d - value %02x", i, data[i] );
[...]
Then I used the command line tool provided with Qtopia to send the
taskbar
the message "Hallo" and this is what I got:
TaskBar::receive - bytearray size 14
TaskBar::receive - byte 0 - value 00
TaskBar::receive - byte 1 - value 00
TaskBar::receive - byte 2 - value 00
TaskBar::receive - byte 3 - value 0a
TaskBar::receive - byte 4 - value 00
TaskBar::receive - byte 5 - value 48
TaskBar::receive - byte 6 - value 00
TaskBar::receive - byte 7 - value 61
TaskBar::receive - byte 8 - value 00
TaskBar::receive - byte 9 - value 6c
TaskBar::receive - byte 10 - value 00
TaskBar::receive - byte 11 - value 6c
TaskBar::receive - byte 12 - value 00
TaskBar::receive - byte 13 - value 6f
Looks pretty much like unicode for me... which, if I had thought more
carefully,
should have been obvious... because QString internally handles
everything as unicode, it is also marshalled as unicode... utf16,
to be specific. This conclusion is also supported by
http://doc.trolltech.com/2.3/qdatastreamformat.html :)
Just for the records, compare this to the output when I send the same
with Python:
TaskBar::receive - bytearray size 9
TaskBar::receive - byte 0 - value 00
TaskBar::receive - byte 1 - value 00
TaskBar::receive - byte 2 - value 00
TaskBar::receive - byte 3 - value 05
TaskBar::receive - byte 4 - value 48
TaskBar::receive - byte 5 - value 61
TaskBar::receive - byte 6 - value 6c
TaskBar::receive - byte 7 - value 6c
TaskBar::receive - byte 8 - value 6f
Cheers,
Mickey.
--
:M:
--
Dipl.-Inf. Michael 'Mickey' Lauer
[EMAIL PROTECTED]
Raum 10b - ++49 69 798 28358 Fachbereich Informatik und Biologie
--
___
PyKDE mailing list[EMAIL PROTECTED]
http://mats.gmd.de/mailman/listinfo/pykde
Re: [PyKDE] QThread problem
You forgot to call the constructor of QThread. Cheers, -- :M: -- Dipl.-Inf. Michael 'Mickey' Lauer [EMAIL PROTECTED] Raum 10b - ++49 69 798 28358 Fachbereich Informatik und Biologie -- ___ PyKDE mailing list[EMAIL PROTECTED] http://mats.gmd.de/mailman/listinfo/pykde
Re: [PyKDE] SIP Roadmap
> http://www.riverbankcomputing.co.uk/sip/roadmap.php Sounds very interesting... great changes to come up. However, as always I'm concerned about the Qt/Embedded and more specifically the QtPE bindings - what is your direction for these? iPAQ and Zaurus developers will have to stick at least another year or so with Qt/E 2.3.x. Cheers, Mickey. -- :M: -- Dipl.-Inf. Michael 'Mickey' Lauer [EMAIL PROTECTED] Raum 10b - ++49 69 798 28358 Fachbereich Informatik und Biologie -- ___ PyKDE mailing list[EMAIL PROTECTED] http://mats.gmd.de/mailman/listinfo/pykde
Re: [PyKDE] MD5 algorithm -help
[sip and md5] You have reached the wrong mailing list. "Our" SIP is a lightweight language binding generator and you were (most likely) referring to the Session Initiation Protocol (SIP) which most of us here know absolutely nothing about. You might want to check the sipforum or just google for more hints. Cheers, -- :M: -- Dipl.-Inf. Michael 'Mickey' Lauer [EMAIL PROTECTED] Raum 10b - ++49 69 798 28358 Fachbereich Informatik und Biologie -- ___ PyKDE mailing list[EMAIL PROTECTED] http://mats.gmd.de/mailman/listinfo/pykde
Re: [PyKDE] pykde.sourceforge.net
Am Mit, 2003-01-15 um 23.05 schrieb Torsten Marek: > What is the future of pyke.sf.net, because I want to know if it is possible to place >some > little programs I happened to write on that page. By now, I do not have my own page >and I > wouldn't like to create one. > So it would be nice if there was a section of programs with links and/or direct >downloads. Yeah, I second this. I have a bunch of (hopefully resuable) PyQt widgets which I could publish and would be interested in seeing other ones. > One of the programs I mean is outline.py. It started as a port of the outline >example of > Qt, but is under development for some time now and has evolved. > It keeps a tree of remarks in an XML file, I use it as todolist/notepad/knowledge > base/organizer. Sounds interesting. Who is in charge of [EMAIL PROTECTED]? -- :M: -- Dipl.-Inf. Michael 'Mickey' Lauer [EMAIL PROTECTED] Raum 10b - ++49 69 798 28358 Fachbereich Informatik und Biologie -- ___ PyKDE mailing list[EMAIL PROTECTED] http://mats.gmd.de/mailman/listinfo/pykde
Re: [PyKDE] pyqt-debian
Am Don, 2003-01-16 um 09.01 schrieb Phil Thompson: > With SIP v4 there won't be any visible version numbers (there will be internal > ones that will trigger an exception if you mix incomatible modules). The > names will be sip.so, qt.so, qttable.so etc. By the way, can you give a *rough* pointer about when v4 will happen? Cheers, Mickey. -- :M: -- Dipl.-Inf. Michael 'Mickey' Lauer [EMAIL PROTECTED] Raum 10b - ++49 69 798 28358 Fachbereich Informatik und Biologie -- ___ PyKDE mailing list[EMAIL PROTECTED] http://mats.gmd.de/mailman/listinfo/pykde
Re: [PyKDE] pykde.sourceforge.net
> Option one is to have some sort of system where one could sign up, post > scripts, rate other's scripts, comments on each other's scripts, offer > patches, etc..., all hosted on SourceForge. This would be a lot of work, and > it needs to be written in PHP. I can't help with this because I don't know > PHP, I don't have the time to learn it, nor the time to implement something > with it. If anyone knows PHP, or wants to learn it, and has time to do the > development, let me know and I'll help get you set up. Take a look at openzaurus.org, which is coded in php. Since I'm very active in this project, I know the guy who did this. Maybe we could take some of this code? Mickey. -- :M: -- Dipl.-Inf. Michael 'Mickey' Lauer [EMAIL PROTECTED] Raum 10b - ++49 69 798 28358 Fachbereich Informatik und Biologie -- ___ PyKDE mailing list[EMAIL PROTECTED] http://mats.gmd.de/mailman/listinfo/pykde
[PyKDE] sip macro expansion
Hi Phil, is it possible to escape a '$' as part of a sip .pro-file template? E.g. if I want to have a line like LIBS = $$(PRESIP_LIBS) (which is a valid qmake construct) to appear in my .pro file, sip swallows the first $ because of the macro expansion. If I try with $$$(PRESIP_LIBS) it complains about an invalid macro. Is there a way to get $$(BLAH) into the resulting .pro - file? Yours, -- :M: -- Dipl.-Inf. Michael 'Mickey' Lauer [EMAIL PROTECTED] Raum 10b - ++49 69 798 28358 Fachbereich Informatik und Biologie -- ___ PyKDE mailing list[EMAIL PROTECTED] http://mats.gmd.de/mailman/listinfo/pykde
Re: [PyKDE] ANNOUNCE: IQtPy for event handling by Python'sread-eval-print loop
Am Son, 2003-02-23 um 19.02 schrieb Gerard Vermeulen: > I am using this little toy for a week and I can't miss it anymore: > it allows me to use the standard Python interpreter running in an > xterm/Eterm/konsole to create and control PyQt widgets, and to use > the widgets at the same time as in a standard GUI program. This is an interesting approach. I took a slightly different one for my EPythonShell Widget - see the attached code. Cheers, -- Michael Lauer <[EMAIL PROTECTED]> Institute of Telematics, CS. Dept., Frankfurt University pythonshell.py Description: application/python
