Hi Thiago,
many thanks for your answer..
== First issue ==
But still I didn't receive the concrete response: as to us to be? :)
In a buffer mode is to use the "deferred" writing or the "immediately"
writing?
This question causes many disputes in our QtSerialPort team ( even, up
to a fight :)
On Thu, Apr 17, 2014 at 7:54 AM, Aleix Pol wrote:
> Hi,
> Yesterday I was trying to figure out a problem I've been having on some code
> that keeps track of screen management changes on my system. After some
> investigation I came to the conclusion that my problem was in Qt [1].
>
> I'm sending th
>Hi.
>
Hi again,
Disclaimer. I don't work for Digia and I have never worked for Digia. I did
work for Trolltech and Nokia though.
>I once again fluently look source codes of Qt and I see that the only one
>I/O class which supports a buffered mode is QTcpSocket (i.e.
>QAbstractSocket in buffere
This is awesome. I'm curious if anyone has tried the Clang static analyzer on
the Qt codebase?
--
Jake Petroules
Chief Technology Officer
Petroules Corporation · www.petroules.com
Email: jake.petrou...@petroules.com
On 2014-04-18, at 07:28 AM, Richard Moore wrote:
> http://www.viva64.com/en/b/
Em sex 18 abr 2014, às 14:32:49, Denis Shienkov escreveu:
> My question most likely belongs to the Qt developers from Digia. For
> example to maintainers of a "network" subsystem.
Note: none of the 3 network maintainers work for Digia.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Softwa
Em sex 18 abr 2014, às 18:14:43, Denis Shienkov escreveu:
> Hi.
>
> I once again fluently look source codes of Qt and I see that the only one
> I/O class which supports a buffered mode is QTcpSocket (i.e.
> QAbstractSocket in buffered mode); in which is used the "deferred" writing
> for data trans
Hi.
I once again fluently look source codes of Qt and I see that the only one
I/O class which supports a buffered mode is QTcpSocket (i.e.
QAbstractSocket in buffered mode); in which is used the "deferred" writing
for data transfer.
Thus, whether can I take such behavior (with "deferred" writing)
On Fri, Apr 18, 2014 at 4:58 PM, Richard Moore wrote:
> http://www.viva64.com/en/b/0251/
Wowsome of the typos are just...wow!
For stuff like:
if (!m)
return m->engine()->currentContext()->throwTypeError();
I'd be surprised we haven't hit this bug already!
Nice find I must say.
-man
Hi,
El 18/04/14 14:25, Ramakanthreddy Kesireddy escribió:
> Iam using Qt5.3 Beta .. However, while trying to use QtLocation 5.3, it
> says module Qt location is not installed.
>
> Am I missing anything?
>
> Thanks and Regards,
>
> Ramakanth
>
As Alex said, Qt Location is not released yet .. so it
Iam using Qt5.3 Beta .. However, while trying to use QtLocation 5.3, it says
module Qt location is not installed.
Am I missing anything?
Thanks and Regards,
Ramakanth
From:
development-bounces+ramakanthreddy.kesireddy=techmahindra@qt-project.org
[mailto:development-bounces+ramakanthreddy.k
http://www.viva64.com/en/b/0251/
I've fixed a few of the copy-paste errors, but I've not gone through the
whole list:
https://codereview.qt-project.org/#change,83763
https://codereview.qt-project.org/#change,83764
https://codereview.qt-project.org/#change,83765
https://codereview.qt-project.org/#
Hi.
My question most likely belongs to the Qt developers from Digia. For
example to maintainers of a "network" subsystem.
I see that in QAbstractSocket::write() in a buffered mode is used the
"deferred" data transmission:
https://qt.gitorious.org/qt/qtbase/source/454dc332b3856c1726683595575c3428
12 matches
Mail list logo
