Re: [Interest] Process isolation with Qt - how to communicate with child processes

2016-01-04 Thread Thiago Macieira
On Monday 04 January 2016 18:47:27 Etienne Sandré-Chardonnal wrote: > This is probably a superstitious/religious belief, I do not like polling > due to the latency/overhead tradeoff that you have to make anyway. Here I > need fairly low latency (about 50ms) so the polling should be at that >

Re: [Interest] Process isolation with Qt - how to communicate with child processes

2016-01-04 Thread Alejandro Exojo
El Monday 04 January 2016, Thiago Macieira escribió: > It works just fine, except on Windows. This was something that I discovered through some pain a while ago. I would go with stdin/out if possible because you don't have to worry about connect(). I recently found that Qt Assistant has a tiny

Re: [Interest] Process isolation with Qt - how to communicate with child processes

2016-01-04 Thread Konstantin Tokarev
04.01.2016, 20:47, "Etienne Sandré-Chardonnal" : > This is probably a superstitious/religious belief, I do not like polling due > to the latency/overhead tradeoff that you have to make anyway. Here I need > fairly low latency (about 50ms) so the polling should be at

Re: [Interest] Process isolation with Qt - how to communicate with child processes

2016-01-04 Thread Alan Ezust
I would recommend using the QProcess class. It emits signals when you need to read data from it. On Mon, Jan 4, 2016 at 9:00 AM, Etienne Sandré-Chardonnal < etienne.san...@m4x.org> wrote: > Dear All, > > I have a server app which currently spawns threads for processing tasks > from incoming

Re: [Interest] Android Studio 1.5.1 with Qt 5.5.1 OSX

2016-01-04 Thread rpzrpz...@gmail.com
Oops, sorry, message double sent. md On 1/3/2016 10:50 PM, mark diener wrote: Hello List: Anybody run into problems with gradle from qt 5.5.1 projects? qt5.6 beta projects: Lots of problems with Gradle not knowing which way is up by opening gradle.build. Error:(37, 0) Could not find

Re: [Interest] Using std::string in android projects

2016-01-04 Thread Jason H
> That's the std::terminate's default handler. That handler is called when an > exception is thrown but not caught. What exception was thrown? Can you put a > catch block to see what it was? I tried that, but it is crashing in not-my-code. I wrapped the areas with try/catch where I use the

[Interest] Qt5.6 not recognised by Visual Studio 2015

2016-01-04 Thread Tom Isaacson
I just downloaded the Qt5.6.0 Beta for 32-bit Visual Studio 2015. I installed the Qt5Package extension but when I run Visual Studio 2015 and select "Add New Qt Version" with the path C:\Qt\Qt5.6.0\msvc2015 I get the error "This Qt version uses an unsupported makefile generator (used:

Re: [Interest] Process isolation with Qt - how to communicate with child processes

2016-01-04 Thread Etienne Sandré-Chardonnal
Hi Alan, I am using QProcess already, but I was talking about the sub-process code itself. Etienne 2016-01-04 21:11 GMT+01:00 Alan Ezust : > I would recommend using the QProcess class. It emits signals when you need > to read data from it. > > > On Mon, Jan 4, 2016 at

Re: [Interest] Android Studio 1.5.1 with Qt 5.5.1 OSX

2016-01-04 Thread mark diener
Bogdan: While I cannot reproduce it reliably, sometimes the Qt "Copy Files to Gradle" will not create a gradle.properties file. That file contains: ## This file is automatically generated by QtCreator. # # This file must *NOT* be checked into Version Control Systems, # as it contains

Re: [Interest] Android Studio 1.5.1 with Qt 5.5.1 OSX

2016-01-04 Thread mark diener
After getting more problems like the one below: Failed to sync Gradle project 'android' Error:Unable to load class 'org.codehaus.groovy.runtime.typehandling.ShortTypeHandling'. Possible causes for this unexpected error include:Gradle's dependency cache may be corrupt (this sometimes occurs after

Re: [Interest] Qt5.6 not recognised by Visual Studio 2015

2016-01-04 Thread Kalinowski Maurice
Please contact the maintainer of the "Qt5Package extension". At least on some other thread people stated that it is broken with VS2015 Update1, but I do not have any first level experience with that thing. Maurice > -Original Message- > From: Interest

Re: [Interest] SOLVED: QStyledItemDelegate's sizeHint() height being ignored by QTableWidget?

2016-01-04 Thread Elvis Stansvik
2016-01-04 16:19 GMT+01:00 Bob Hood : > On 1/3/2016 7:30 PM, Bob Hood wrote: > > Am I going to have to use a QTableView with a model in order to get the > height I need in each cell, or might this be a bug? > > > Since all my images are the same height, I solved this by

Re: [Interest] SOLVED: QStyledItemDelegate's sizeHint() height being ignored by QTableWidget?

2016-01-04 Thread Bob Hood
On 1/4/2016 8:38 AM, Elvis Stansvik wrote: 2016-01-04 16:19 GMT+01:00 Bob Hood : On 1/3/2016 7:30 PM, Bob Hood wrote: Am I going to have to use a QTableView with a model in order to get the height I need in each cell, or might this be a bug? Since all my images are the

Re: [Interest] SOLVED: QStyledItemDelegate's sizeHint() height being ignored by QTableWidget?

2016-01-04 Thread Bob Hood
On 1/3/2016 7:30 PM, Bob Hood wrote: Am I going to have to use a QTableView with a model in order to get the height I need in each cell, or might this be a bug? Since all my images are the same height, I solved this by directly calling QTableWidget's inherited method setRowHeight(). This has

Re: [Interest] Process isolation with Qt - how to communicate with child processes

2016-01-04 Thread Konstantin Tokarev
04.01.2016, 20:00, "Etienne Sandré-Chardonnal" : > Dear All, > > I have a server app which currently spawns threads for processing tasks from > incoming connections. > > I need to isolate these tasks in processes instead of threads (there are > several reasons for this,

Re: [Interest] Process isolation with Qt - how to communicate with child processes

2016-01-04 Thread Konstantin Tokarev
04.01.2016, 20:00, "Etienne Sandré-Chardonnal" : > Dear All, > > I have a server app which currently spawns threads for processing tasks from > incoming connections. > > I need to isolate these tasks in processes instead of threads (there are > several reasons for this,

Re: [Interest] Process isolation with Qt - how to communicate with child processes

2016-01-04 Thread Etienne Sandré-Chardonnal
Thanks to all. I did not know about QLocalSocket. I will definitely have a look. Yes, stdin can be used in both blocking and non-blocking mode, but how to avoid polling and callback upon data is available? This would imply running a dedicated thread for blocking read and send a queued signal.

Re: [Interest] Process isolation with Qt - how to communicate with child processes

2016-01-04 Thread Konstantin Tokarev
04.01.2016, 20:28, "Etienne Sandré-Chardonnal" : > Thanks to all. > > I did not know about QLocalSocket. I will definitely have a look. > > Yes, stdin can be used in both blocking and non-blocking mode, but how to > avoid polling and callback upon data is available? This

Re: [Interest] Process isolation with Qt - how to communicate with child processes

2016-01-04 Thread Etienne Sandré-Chardonnal
This is probably a superstitious/religious belief, I do not like polling due to the latency/overhead tradeoff that you have to make anyway. Here I need fairly low latency (about 50ms) so the polling should be at that interval at most. Also, I would bet that QSocketNotifier does not work with

Re: [Interest] Process isolation with Qt - how to communicate with child processes

2016-01-04 Thread Giuseppe D'Angelo
On Mon, Jan 4, 2016 at 6:00 PM, Etienne Sandré-Chardonnal wrote: > What is the best Qt way to communicate with the child processes? I have > first thought using standard input/output, but it seems that it's impossible > to wait for incoming data from stdin without polling.

[Interest] Process isolation with Qt - how to communicate with child processes

2016-01-04 Thread Etienne Sandré-Chardonnal
Dear All, I have a server app which currently spawns threads for processing tasks from incoming connections. I need to isolate these tasks in processes instead of threads (there are several reasons for this, including the fact that tasks will run possibly bugged plugin code and this should not