Re: [Interest] Curious QNetworkAccessManager behavior.

2019-10-31 Thread Tony Rietwyk
Hi Jason, You should only connect to QNetworkAccessManager::finished once - before sending any files.  You are adding another connection with each file. From https://doc.qt.io/qt-5/qobject.html: By default, a signal is emitted for every connection you make; two signals are emitted for

[Interest] Curious QNetworkAccessManager behavior.

2019-10-31 Thread Jason H
I'm uploading files with QNAM. QFile *file = new QFile(QString("%1/%2/%3").arg(_dataDir).arg(SERVER_SYNC_DIR).arg(filename)); if (file->open(QIODevice::ReadOnly)) { QNetworkRequest req(QUrl(QString("%1/%2/%3").arg(_serverUrl.toString()).arg("post").arg(filename)));

Re: [Interest] Qml Canvas is too slow

2019-10-31 Thread Jason H
Very simply, you don't have to repaint the entire thing every time. You can paint the squares, then fill them in one by one. You're essentiallt re-drawing over already dorawn pixels.     Sent: Thursday, October 31, 2019 at 11:42 AM From: "Alexander Dyagilev" To: "interest@qt-project.org"

Re: [Interest] Qml Canvas is too slow

2019-10-31 Thread Nuno Santos
Alexander, Why do you want to stick to pure Qml? What are the reasons? -- Nuno Santos No dia 31/10/2019, às 18:13, Alexander Dyagilev escreveu: > Thanks for the answer. > > This means I'll have to use c++. But I was asking for a way to stick with a > pure QML. > > > >> On 10/31/2019

Re: [Interest] QGraphicsObject::boundingRect() called with different instance

2019-10-31 Thread Bob Hood
On 10/31/2019 3:07 AM, Giuseppe D'Angelo wrote: Il 31/10/19 01:55, Bob Hood ha scritto: I'm on Windows using Qt Creator 4.6.2. Apart from MSVC working on porting ASAN, there's a memory error detector available as part of Intel Studio. To me, valgrind/ASAN is still a _huge_ reason to prefer

Re: [Interest] Qml Canvas is too slow

2019-10-31 Thread Jérôme Godbout
Maybe not as fast or future proof, but Maybe a simple Item Rectangle of each type (full and empty) and use a repeater of Qml ShaderEffect {} to duplicate the rendering, may lead to decent performance. Not sure if this will be good enough. [36E56279] une compagnie

Re: [Interest] Qml Canvas is too slow

2019-10-31 Thread Alexander Dyagilev
Thanks for the answer. This means I'll have to use c++. But I was asking for a way to stick with a pure QML. On 10/31/2019 7:52 PM, Nuno Santos wrote: Alexander, You should use QtQuick Scene Graph. It will be 100x faster. Look for examples on QtCreator under the welcome tab. Use the

Re: [Interest] Qml Canvas is too slow

2019-10-31 Thread Nuno Santos
Alexander, You should use QtQuick Scene Graph. It will be 100x faster. Look for examples on QtCreator under the welcome tab. Use the search input box and write “scene graph”. Scene Graph - Custom Geometry Scene Graph - Graph If it is the first time, it might look confusing but it will pay

[Interest] Qml Canvas is too slow

2019-10-31 Thread Alexander Dyagilev
Hello, The following code is too slow (paint operation takes few seconds): Canvas{ id:map width:columnsCount*rectangleSize height:rowsCount*rectangleSize anchors.horizontalCenter:alignCenter?parent.horizontalCenter:undefined anchors.left:alignCenter?undefined:parent.left

Re: [Interest] QGraphicsObject::boundingRect() called with different instance

2019-10-31 Thread Giuseppe D'Angelo via Interest
Il 31/10/19 01:55, Bob Hood ha scritto: I'm on Windows using Qt Creator 4.6.2. Apart from MSVC working on porting ASAN, there's a memory error detector available as part of Intel Studio. To me, valgrind/ASAN is still a _huge_ reason to prefer Linux development. If you can, get a testcase

Re: [Interest] QGraphicsObject::boundingRect() called with different instance

2019-10-31 Thread alexander golks
Am Wed, 30 Oct 2019 18:55:04 -0600 schrieb Bob Hood : > (Sorry for the slow reply.  F#@$ing Comcast decided yesterday that all my > mailing list traffic was Spam.) > > > On 10/30/2019 5:17 AM, Giuseppe D'Angelo via Interest wrote: > > On 30/10/2019 01:47, Bob Hood wrote: > >> When I enter