Ok, let's use QtWin for the namespace. For the module itself it makes IMO
to keep the 'Extras' in the name.
Cheers,
Lars
On 06.09.13 15:52, "Sorvig Morten" wrote:
>I agree, QtWin::foo looks much better. We can rename the QtMacExtras
>namespace as well.
>
>What about the module name itself? Woul
Full agreement with Konstantin. It's two weeks before the feature freeze and we
haven't seen any more then a draft. I am against any new classes going into Qt
essential modules that do not have direct and proven use cases.
Develop it in a playground project, show why it makes sense and once you
2013/9/9 Sune Vuorela
> The api has been stabilized and well tested since like forever.
>
> Let's get a QAbstractJob heavily inspired by KJob in now.
>
> A nice side effect of getting it in now is that the myriad of nice
> frameworks KDE is preparing for ship could be built on QAbstractJob and
>
On Friday 06 September 2013 17:20:59 Thiago Macieira wrote:
> On sexta-feira, 6 de setembro de 2013 19:52:47, David Faure wrote:
> > * relation to QNetworkReply?
> > If that one didn't exist yet, we'd definitely write it as a QJob subclass.
> > So instead, I propose to wrap QNetworkReply into a QN
On 9 September 2013 19:38, David Faure wrote:
>
>
> I understand that you want to limit the growth of QtCore, but, hmm, a separate
> library/module QtJobs seems very strange. It's not like it's separate
> technology, the core of QAbstractJob's technology is the QtCore event loop.
> Can you see you
On segunda-feira, 9 de setembro de 2013 19:38:20, David Faure wrote:
> I still think the best solution is:
> QtCore: QAbstractJob, and later QProcessJob and QThreadJob
> QtNetwork: QNetworkRequestJob (wrapping QNetworkReply)
> QtDBus: (later) QDBusCallJob (wrapping QDBusPendingCallWatcher)
>
> The
Thanks Shane! I'm aware of the workaround, I just didn't know that
Webkit's WS implementation was not bound to the QNetworkAccessManager.
With a little source code reading, I think it would not be possible to
manage network connection from an unique entry point to all my Qt based
apps. I'll hav
If you wanted to access a websocket service from native c++ or from QML
javascript, it would be quite hard to use webkit's implementation.
I expect you'd have to invoke some javascript inside the webkit engine to
do the request for you and get a result.
Websocket is an unpleasant workaround to the
moveToThread on a socket should do the following:
1. cancel socket notifiers
2. change thread affinity
3. (in new thread) re-enable socket notifiers.
Could be that step 1 doesn't remove already pending notifications when
using the gnome event dispatcher.
For a safe multithreaded server, you shoul
On 2013-09-09, Giuseppe D'Angelo wrote:
> Indeed, but how about starting with an addon and then moving the
> classes inside QtCore? We can freely break API/ABI in addons -- when
> things get stabilized, we start including them in QTCore/QtNetwork...
I'm not sure what a addon containing 1 small cl
On Mon, Sep 9, 2013 at 3:21 PM, BogDan wrote:
> I'm trying to stage this https://codereview.qt-project.org/#change,64292
> patch, but CI complains that 2 files don't contain "a license header". But
> I'm pretty sure they do.
At a guess, they are there, but aren't valid. Date ranges aren't
a
Hello,
I'm trying to stage this https://codereview.qt-project.org/#change,64292
patch, but CI complains that 2 files don't contain "a license header". But I'm
pretty sure they do.
Some please help :) !
Cheers,
BogDan.
___
Development mailing list
Hi,
as some of you might have heard we are planning to get qtbase's winrt
branch integrated to dev in order to have a tech preview available at
least for that part of Qt. In order to have it reviewed properly it
would be awesome if some of you could have a look at the "winrt" topic
branch
(http
Hello,
i'm currently stress-testing a application at work and came across this
problem.
The application accepts connections and pushes the created sockets
to a worker thread (moveToThread), the worker thread then handles the
rest.
But sometimes when the socket was already closed in the thread i
ge
What are the exact conditions when Qt may repaint an a screen?
I am interested in any visual change of a monitor screen. Hence, it is
sensible to wait for any repaint event.
E.g. in Windows it is repainted accord. to MSDN when
a control element is resized, moved, exposed after being covered by anot
15 matches
Mail list logo
