On May 20, 2014, at 2:16 PM, Paul Miller wrote:
> Your best bet is to do your "work" in a thread while .exec()ing the
> dialog. Then the main window UI's event loop can spin normally.
In my case, the code that executes is not thread-safe. It's ancient,
complicated code. If I try to make it thr
Em ter 20 maio 2014, às 23:11:06, mai...@virtual-winds.org escreveu:
> I'm doing processEvent() just to make sure the dialog is painted before
> an heavy treatment. Basically it shows "Please wait" while the process
> is running. I guess I am not the only one doing such things... If I
> don't call
> I want to show(), do something, and then delete the messagebox. Not just
> show() and return, what would be the point? I don't want to exec()
> because I don't want the user to need to click on something, it's just a
> waiting message that should not block the execution.
>
> It works fine on 521
I'm doing processEvent() just to make sure the dialog is painted before
an heavy treatment. Basically it shows "Please wait" while the process
is running. I guess I am not the only one doing such things... If I
don't call processEvents on some platforms the dialog is just half
painted, probably
Nurmi J-P schreef op 19-5-2014 14:29:
> On 19 May 2014, at 12:51, Alexander Ivash wrote:
>
>> I was trying to use QML components in simple android application but
>> confronted several issues:
>>
>> 1. I couldn't find any API allowing to adjust widths of columns in TableView
>> based on the cont
>> 1. I couldn't find any API allowing to adjust widths of columns in
>> TableView based on the content. Do I understand right that the only way
>> to achieve this is to go through all the entries in model manually and
>> calculate maximum width using 'paintedWidth' of Text element? Does the
In my case, we're creating a kind of progress window. The code that runs while
the dialog is up is rather old and not thread-safe. But using Qt before 5.3 I
can show the dialog, run the computation, adjust the information in the dialog
and call processEvents to cause it to repaint and to allow t
Em ter 20 maio 2014, às 19:04:39, mai...@virtual-winds.org escreveu:
> Thanks for your reply
>
> Why is removing the processEvent the right thing to do?
Because processEvents() means nested event loops. You shouldn't do that. You
should show() and then return;, so the non-nested event loops resu
Indeed it's the same problem. For us it's a blocker and mac/os users
will have to stay under 521 until it's fixed.
Philippe Lelong
Le 20-05-2014 19:19, John Weeks a écrit :
> Sounds like the same problem I ran into:
> https://bugreports.qt-project.org/browse/QTBUG-38874
>
> -John Weeks
>
>
>
Sounds like the same problem I ran into:
https://bugreports.qt-project.org/browse/QTBUG-38874
-John Weeks
On May 20, 2014, at 10:04 AM, mai...@virtual-winds.org wrote:
> Thanks for your reply
>
> Why is removing the processEvent the right thing to do?
>
> Anyhow if I remove it, the event loo
Thanks for your reply
Why is removing the processEvent the right thing to do?
Anyhow if I remove it, the event loop is locked anyway, and no more
events are processed. So imo the processEvents just highlights the
problem, it's not the cause of it. Also note that I have similar
sequences in oth
Em ter 20 maio 2014, às 18:39:41, mai...@virtual-winds.org escreveu:
> If I run this under 530/MacOS, I see only up to "step 4" in the console.
> If I remove processEvents() it continues, but I have problems later for
> instance doing deleteLater() which never calls the destructor. As it
> seems
Hello,
I have a problem reported by my MAC/OS testers with the brand new 530
official release. As it seems, there is a problem with
QMessageBox::show() which seems to be blocking eventLoop.
The sequence is like that:
qWarning()<<"step 1";
waitBox = new
QMessageBox(QMessageB
Em ter 20 maio 2014, às 16:01:29, Jason Hihn escreveu:
> I can appreciate that the API is unstable, and jsut putting
> that in the documentation as /* THAR BE DRAGONS HERE */ (which I've
> seen in actual code somewhere, not necessarily Qt) or something to that
> affect would be sufficient.
We're n
Per http://qt-project.org/wiki/Licensing-talk-about-mobile-platforms ,
The specific statement in question is " It remains to be seen whether Apple will accept applications that bundle dylibs into the iOS App Store"
Do we have a better idea of waht the situation on iOS is?
___
I can appreciate that the API is unstable, and jsut putting that in the documentation as /* THAR BE DRAGONS HERE */ (which I've seen in actual code somewhere, not necessarily Qt) or something to that affect would be sufficient.
I myself in the course of trying vaudeville found a lot of calls chang
On 20 May 2014 15:37, Tomasz Olszak wrote:
> It's not that it is hidden. It's private so that it can change in next
> non patch version. You can use it on your own responsibility and many
> developers, especially in embedded world, do that.
> Minimal documentation is a fact, anyone can change that
2014-05-20 15:23 GMT+02:00 Tomasz Siekierda :
> On 20 May 2014 14:17, Knight Andrew wrote:
>>> Where are the docs?
>>
>> QPA is an internal API, so don't expect any formal documentation or
>> compatibility promises.
>
> I don't think this is a good idea to hide the documentation for QPA...
> Qt i
> -Original Message-
> From: Tomasz Siekierda [mailto:sierd...@gmail.com]
> Sent: 20 May 2014 16:23
> To: Knight Andrew
> Cc: Jason H; interest@qt-project.org
> Subject: Re: [Interest] STILL LOOKING for a QPA
>
> On 20 May 2014 14:17, Knight Andrew wrote:
> >> Where are the docs?
> >
> >
On 20 May 2014 14:17, Knight Andrew wrote:
>> Where are the docs?
>
> QPA is an internal API, so don't expect any formal documentation or
> compatibility promises.
I don't think this is a good idea to hide the documentation for QPA...
Qt is advertised as cross-platform, and since Qt 5 the motto
Hi,
> From: interest-bounces+andrew.knight=digia@qt-project.org
> [mailto:interest-> bounces+andrew.knight=digia@qt-project.org] On Behalf
> Of Jason H
> Sent: 20 May 2014 15:09
> To: interest@qt-project.org
> Subject: [Interest] STILL LOOKING for a QPA
>
> About once a month now I get a
About once a month now I get an off-list request for Vaudeville. There is interest. But I have to say its not ready because I don't know how to make a QPA plugin. It was released with 4.8, API was supposed to be stable by 5.0. QPA is being used on the various platforms. We are up to 5.3 now.
Wher
The quart you have isn't a list of the same things. You have an arrangement of different things in a scroll view.
--
Sent from my Android phone with GMX Mail. Please excuse my brevity."m...@rpzdesign.com" wrote:
Hello QTers:
After pouring through available online documentati
On Tuesday, May 20, 2014 11:21:19 Konrad Rosenbaum wrote:
> Hi,
>
> how did you try to build this? Did you use qmake, plain make, cmake, ...?
>
> However, I think you do need a constructor for classes that are processed
> by moc - at least it is good style to provide one. One like this would be
>
Hi,
how did you try to build this? Did you use qmake, plain make, cmake, ...?
However, I think you do need a constructor for classes that are processed
by moc - at least it is good style to provide one. One like this would be
sufficient:
C++-98: NewTest(){}
C++-11: NewTest()=default;
Also, it i
2014-05-20 2:01 GMT+02:00 Thiago Macieira :
> Em seg 19 maio 2014, às 23:10:10, André Pönitz escreveu:
> > > It's due to the hash randomisation. This was done to avoid DoS attacks
> > > that
> > > can be performed by tweaking data to ensure it always falls into the
> same
> > > hash bucket.
> >
>
Em ter 20 maio 2014, às 08:16:18, BOUCARD Olivier escreveu:
> Why https://bugreports.qt-project.org/browse/QTIFW-441 didn't make it in
> this release?
Because the task is still open. If you click the link to the change, you'll
see why it's still open.
--
Thiago Macieira - thiago.macieira (AT) in
> Subject: [Interest] Qt Quick 2.x Complex ListView
>
> Hello QTers:
> Does anybody have an idea on how to create each row of the listview with a
> delegate that allows for each row > to be rendered with separate logic
> instead of the standard delegate which renders each row with the same or >
Hi guys,
Can someone tell me how do I change the repo for the Qt Maintenance Tool?
I wanted to update to Qt 5.3 and QtCreator 3.1. But it is too slow (5KB/s at
most) out of the 32Mbits/s line...
I'm in Cyprus, so probably the chosen repo is not good.
Why https://bugreports.qt-project.org/browse/
29 matches
Mail list logo
