Am 22.05.2012 00:15, schrieb Erik Janssens:
you could give Camelot a try ...
http://www.python-camelot.com/
Is Camelot usable with Python 3? I can't find out for sure from the
website, but I suspect it's not (Windows installer only for Python 2.7).
Thank you,
Sibylle
Hi,
I wanted to point out a very odd behavior (which is not that odd
actually, but still...)
The documentation says that QDataStream.writeUInt8 and
QDataStream.writeInt8 should be passed a str rather than an int, which
looks strange to me.
http://www.riverbankcomputing.co.uk/static/Docs/PyQt4/ht
Hi,
2012/5/26 Mickaël THOMAS :
> Hi,
>
> I wanted to point out a very odd behavior (which is not that odd
> actually, but still...)
>
> The documentation says that QDataStream.writeUInt8 and
> QDataStream.writeInt8 should be passed a str rather than an int, which
> looks strange to me.
>
> http://
> Type quint8 is an unsigned byte so I think that char is better solution.
> http://qt-project.org/doc/qt-4.8/qdatastream.html#operator-lt-lt-3
What do you mean by "char is a better solution" ?
q(u)int8 is supposed to represent an 8-bit (un)signed number, and the
documentation says "unsigned byte
Hi,
2012/5/26 Mickaël THOMAS :
>> Type quint8 is an unsigned byte so I think that char is better solution.
>> http://qt-project.org/doc/qt-4.8/qdatastream.html#operator-lt-lt-3
>
> What do you mean by "char is a better solution" ?
>
Precision and range of a variable is the same.
> q(u)int8 is su
> Ok, so what is the difference between 8-bit unsigned int and 8-bit
> unsigned char?
Most of the time, when you use "unsigned char" in C/C++, that's
because you're considering your data to be bytes and not characters
(otherwise you just use char)
> unsigned char could be also treated like one-lo
