Hi,
I'll have to read and analyze this code in more detail to give you a qualified
opinion. I'll do this later...
On the surface it looks a bit complicated and I'm not entirely sure about the
seeding, but I'll have to study the API first to make sure.
On Sunday, Sunday 09 February 2014 at 22:4
Em seg 10 fev 2014, às 11:45:31, Denis Shienkov escreveu:
> > Yes, profile it and let us know where the exact problem is.
>
> Ok, thanks. I will try do it as will have a free time.
Last time I profiled our I/O code, the hotspot was memcpy. We copy data far too
often.
--
Thiago Macieira - thia
>That's a wrong conclusion. Our direct implementations of select() (like in
>QProcess and QAbstractSocket) do not use QSocketNotifier. They bypass the
>notifiers and go straight to select.
Yes, they bypass in case of waitForXX() methods.
But I'm talk about QSocketNotifier which also is used in QAb
I allow expression without range limit for example:
ui->label().foo()
or
ui.foo().test()->boo()
and etc.
and I added my patch and added you as a reviewer (
https://codereview.qt-project.org/#change,77758).
2014-02-08 3:32 GMT+06:00 Olivier Goffart :
> On Friday 07 February 2014 14:05:09 Svetkin
Hello All,
I am trying to find the qmake variable that could be used to differentiate
between the iPhone simulator and iPhone arm kits.
In my .pro file, I would like to use conditions like
1.
ios {
2.
CONFIG += c++11
3.
iphonesimulator {
4.
message("iphonesimulator")
5.
On Sunday 09 February 2014 22:40:22 Kurt Pattyn wrote:
> If I use std::random as Thiago proposed (see
> http://en.cppreference.com/w/cpp/numeric/random), like:
>
> //one time initialisation
> Q_CONST_EXPR std::size_t numSeeds = 13; //arbitrary number
> quint32 seeds[numSeeds] = { 0 }
On 29 Jan 2014, at 09:45, Konrad Rosenbaum wrote:
>
> 1) create a fresh TCP connection for each Websocket, this way it is not
> possible to combine a previous HTTP request and a socket in an attack;
> consequently: if the handshake fails: terminate the TCP connection!
This is already happenin
Em dom 09 fev 2014, às 23:26:29, Denis Shienkov escreveu:
> It seems that select() which implicitly uses QSocketNotifier/Dispatcher
> is a bottleneck. But it is very strange
> because the serial port is very slow device on the relation with others.
> Therefore in the theory the I/O with
> the seria
Hi all.
In development of QtSerialPort faced an unpleasant thing - big loading
of CPU in the process of I/O.
A short results can be see here:
https://bugreports.qt-project.org/browse/QTBUG-36684
This loading very big in Linux (up to 30% on 115200 baud) even at using
one instance of the serial
On 9 February 2014 14:56, Bruno Coudoin wrote:
> Hi,
>
> For those who don't know me, I am the author of the educational software
> GCompris (http://gcompris.net). The project started in 2000 and is based
> on Gtk+.
>
> As you imagine, many users are requesting us a tablet version of
> GCompris an
Hi,
For those who don't know me, I am the author of the educational software
GCompris (http://gcompris.net). The project started in 2000 and is based
on Gtk+.
As you imagine, many users are requesting us a tablet version of
GCompris and I tried to evaluate the different technical possibilities
11 matches
Mail list logo
