On sexta-feira, 17 de junho de 2016 15:54:28 PDT Matthew Woehlke wrote:
> > So, you're suggesting not doing anything now, leave std::chrono support
> > out in Qt 5, and do it only for Qt 6?
>
> I'm suggesting that a possible solution to the problem is to return a
> single complex type¹ that can be
On 2016-06-10 19:27, Thiago Macieira wrote:
> On sexta-feira, 10 de junho de 2016 16:12:10 PDT Matthew Woehlke wrote:
>> On 2016-06-10 13:53, Thiago Macieira wrote:
>>> I've added a set of std::chrono API to QTimer[1] and QDeadlineTimer[2] and
>>> we're hitting a snag on what to name the getters. T
On Friday 10 June 2016 19:53:00 Thiago Macieira wrote:
> I've added a set of std::chrono API to QTimer[1] and QDeadlineTimer[2] and
> we're hitting a snag on what to name the getters. The setters are fine
> because they're just overloads:
>
> timer.setInterval(3); // Qt; millisecon
On sexta-feira, 10 de junho de 2016 16:12:10 PDT Matthew Woehlke wrote:
> On 2016-06-10 13:53, Thiago Macieira wrote:
> > I've added a set of std::chrono API to QTimer[1] and QDeadlineTimer[2] and
> > we're hitting a snag on what to name the getters. The setters are fine
> > because>
> > they're j
On 2016-06-10 13:53, Thiago Macieira wrote:
> I've added a set of std::chrono API to QTimer[1] and QDeadlineTimer[2] and
> we're hitting a snag on what to name the getters. The setters are fine
> because
> they're just overloads:
>
> timer.setInterval(3); // Qt; milliseconds
>
I've added a set of std::chrono API to QTimer[1] and QDeadlineTimer[2] and
we're hitting a snag on what to name the getters. The setters are fine because
they're just overloads:
timer.setInterval(3); // Qt; milliseconds
timer.setInterval(3ms);
deadline.setRemain
