Hi, not sure if this would look funny (would it?), but may be referencing
the stock documentation page at
http://doc.qt.io/qt-5.9/threads-reentrancy.html could help avoid further
confusion (and unnecessarily heating the thread).
On Sat, Sep 30, 2017 at 12:50 AM,
wrote:
> Send Development maili
Hi, a commit was just pushed to
https://codereview.qt-project.org/#/c/138645/ .
The logic follows what was discussed / suggested in the previous emails in
this thread, with some additions.
Best regards,
Vladimir
On Wed, Aug 26, 2015 at 7:59 PM, Vladimir Moolle wrote:
> Hi,
>
> >&g
users that ButtonBox
or Dialog.buttonRole is the new way of declaring standard buttons?
With that in mind, and if there are no serious objections, we’d like to
begin implementing a patch tomorrow.
Best regards, Vladimir
On Wed, Aug 26, 2015 at 11:13 AM, Curtis Mitch <
mitch.cur...@theqtcompany.com&
at just yet.
>
> >
> > F.
> >
> > Il 22/ago/2015 13:57, "Curtis Mitch" ha
> scritto:
> >
> >
> > From: development-bounces+mitch.curtis=theqtcompany@qt-project.org
> on
> behalf of Vladimir Moolle
> > Sent: Saturday, 22 August
opup window itself
> and reports the user's choice(s), while QDialogButtonBox manages the
> buttons (something to consider for Qt Quick 3?)
>
>
> On 22 August 2015 at 07:22, Vladimir Moolle wrote:
> >
> > Hi, I’d like to discuss approaches to API design in the context of
Hi, I’d like to discuss approaches to API design in the context of
https://bugreports.qt.io/browse/QTBUG-47850 (making Quick Controls dialogs’
standard buttons’ enabled properly state accessible).
It seems, that the desired properties of an API implementing the above
would be:
possibility to decla
