On Mon 30-Apr-07, Danny Pansters wrote:
> On Monday 30 April 2007 16:46:59 you wrote:
> > > It seems I can't retrieve a QString object containing non-ASCII
> > > characters.
> >
> > You can if you use unicode() instead of str().
>
> Yes that's obvious, but it may break other people's apps when usin
On Monday 30 April 2007 21:35:57 Hans-Peter Jansen wrote:
> Am Montag, 30. April 2007 16:22 schrieb Danny Pansters:
> > The code that does the video capturing is written in C and used in the
> > rest of the app as a python module (using SWIG to expose a dozen simple
> > control functions).
>
> You
On Monday 30 April 2007 16:46:59 you wrote:
> > It seems I can't retrieve a QString object containing non-ASCII
> > characters.
>
> You can if you use unicode() instead of str().
Yes that's obvious, but it may break other people's apps when using such a
patched dcopext module. I create and mainta
Am Montag, 30. April 2007 16:22 schrieb Danny Pansters:
>
> The code that does the video capturing is written in C and used in the
> rest of the app as a python module (using SWIG to expose a dozen simple
> control functions).
You may want to do yourself a favour and wrap that stuff with sip. Tha
On Mon 30-Apr-07, Danny Pansters wrote:
> Hi,
>
> It seems I can't retrieve a QString object containing non-ASCII characters.
You can if you use unicode() instead of str().
> I have a TV application (on FreeBSD) and it exports most of its functions
> via dcop. I now added functionality to retrie
Hi,
It seems I can't retrieve a QString object containing non-ASCII characters. I
have a TV application (on FreeBSD) and it exports most of its functions via
dcop. I now added functionality to retrieve (raw YUV) framedata over dcop,
the idea being to eventually write a minimal dcopclient in C++
