Re: [Interest] Is it safe to use QString::utf16() as a Windows wchar_t*?

2017-11-09 Thread André Pönitz
On Thu, Nov 09, 2017 at 11:15:28AM +0200, Nikos Chantziaras wrote: > On Windows, I use this: > > void func(const wchar_t*); > QString s; > > // ... > > func(reinterpret_cast(s.utf16())); > > This saves an allocation, a copy and a free since I don't have to use > QString::toWCharArray().

[Interest] Embed MyScript editor in QWidget?

2017-11-09 Thread Patrick Stinson
Hello! Has anyone successfully embedded a MyScript UIView in a QWidget for handwriting recognition? I am no iOS expert, thought I would ask before I spend two weeks reading Apple docs to sort out the delegate/viewcontroller/etc mess. Thanks! -Patrick smime.p7s Description: S/MIME cryptographic

Re: [Interest] QtMqtt

2017-11-09 Thread Maurice Kalinowski
In the middle of another change, but try to change it to: m_payload.append(data.constData(), data.size()); Reason is that at around 35MB you get a null, hence it stops. If you specify the size of the data, QByteArray will take the argument as for granted. Maurice From: Filip Piechocki [mailto

Re: [Interest] QtMqtt

2017-11-09 Thread Filip Piechocki
Hi, Was playing a bit with QtMqtt and written some example publisher that shares files from a specific directory. Each file contents is sent as a one message on /dirName/fileName topic so a subscriber subscribes on /dirName/+ Along the files there was an 35MB mp4 file (so way below MQTT's ~256MB l

Re: [Interest] Need advice to add tests to an existing, project

2017-11-09 Thread Roland Hughes
On 11/08/2017 04:02 AM, Christian Gagneraud wrote: On 8 November 2017 at 13:35, Roland Hughes wrote: Back in the days of the VAX 11/750 all of that microcode (what it was called I know VACOS (VAcuum Cleaner Operated System) but I do not know VAX, sorry! ;) This site has a picture, but pretty m

Re: [Interest] Is it safe to use QString::utf16() as a Windows wchar_t*?

2017-11-09 Thread Konstantin Tokarev
09.11.2017, 12:16, "Nikos Chantziaras" : > On Windows, I use this: > >    void func(const wchar_t*); >    QString s; > >    // ... > >    func(reinterpret_cast(s.utf16())); > > This saves an allocation, a copy and a free since I don't have to use > QString::toWCharArray(). However, is this actual

Re: [Interest] Is it safe to use QString::utf16() as a Windows wchar_t*?

2017-11-09 Thread Giuseppe D'Angelo
Il 09/11/2017 10:15, Nikos Chantziaras ha scritto: This saves an allocation, a copy and a free since I don't have to use QString::toWCharArray(). However, is this actually safe? "It seems to work," and AFAIK, QString::d->data() is already in the format and encoding Windows excepts a wchar_t* to b

[Interest] Qt 5.9.1 for Android 4.0

2017-11-09 Thread Filip Piechocki
Hi, I would like to use Qt 5.9.1 on Android 4.0 but docs say that at least Android 4.1 is required. Is there any workaround for that? Like for example some module requires it and we can just not use it in our deployment? What in Qt 5.9.1 requires API level 16? BR, Filip ___

[Interest] Is it safe to use QString::utf16() as a Windows wchar_t*?

2017-11-09 Thread Nikos Chantziaras
On Windows, I use this: void func(const wchar_t*); QString s; // ... func(reinterpret_cast(s.utf16())); This saves an allocation, a copy and a free since I don't have to use QString::toWCharArray(). However, is this actually safe? "It seems to work," and AFAIK, QString::d->data() is