On Friday, 24 July 2020 10:32:08 PDT Ville Voutilainen wrote:
> I don't know what the "sub-scope of a class" means.
struct S
{
namespace prop1 {
int operator()() const;
void bind(std::function binding;
};
private:
int propvalue;
}
int S::prop1::operator()() const
{
On Fri, 24 Jul 2020 at 22:24, Lisandro Damián Nicanor Pérez Meyer
wrote:
> > A few years ago, Gtk threatened to do that starting with Gtk 4:
> > https://lwn.net/Articles/691131/
> > https://blogs.gnome.org/desrt/2016/06/13/gtk-4-0-is-not-gtk-4/
> > https://blogs.gnome.org/desrt/2016/06/14/gtk-5-0
Hi!
On Fri, 24 Jul 2020 at 09:10, Pier Luigi Fiorini
wrote:
>
> Il giorno gio 16 lug 2020 alle ore 10:11 Shawn Rutledge
> ha scritto:
>>
>>
>> > On 2020 Jul 6, at 18:57, Pier Luigi Fiorini
>> > wrote:
>> >
>> > Hi,
>> >
>> > I noticed that some modules are going into the marketplace, for exam
Hi!
With my Debian Qt maintainer hat on: I want to stress everything that
Thiago mentioned in the cited below mail. Rebuilding the entire Qt
world in a distribution is a tremendous huge task. I'm afraid I can't
express the pain it is specially for libraries as popular as Qt... try
it yourself mayb
On Fri, 24 Jul 2020 at 18:10, Thiago Macieira wrote:
> Can I suggest that we prepare at least two papers for the standard? One for
> the member-to-containing-object trick and the second for what QProperty really
> is: sub-scope of a class. We don't want a different this pointer, we just want
> to
On Friday, 24 July 2020 08:27:54 PDT Stottlemyer, Brett (B.S.) wrote:
> ... what QProperty really
> is: sub-scope of a class. We don't want a different this pointer, we
> just want to scope.
>
> Is QProperty really a sub-scope? Many of the examples are not tied to
> objects (QObject or
On 7/24/20, 11:09 AM, "Development on behalf of Thiago Macieira"
wrote:
... what QProperty really
is: sub-scope of a class. We don't want a different this pointer, we just
want
to scope.
Is QProperty really a sub-scope? Many of the examples are not tied to objects
(QObject or
On Friday, 24 July 2020 00:20:46 PDT Olivier Goffart wrote:
> You do not need to use the empty array everywhere: only in the helper type
> created by the Q_PRIVATE_QPROPERTY macro. And it can be conditioned on
> pre-c++20 GCC.
The problem is that it is in QObject and other Qt classes. That's why I
On Friday, 24 July 2020 04:16:31 PDT Stottlemyer, Brett (B.S.) wrote:
> This is new. Are you positing that this evaluation mode should exist? Or
> is it already how the implementation works?
It should exist, if it doesn't yet.
> What determines whether a slot supports lazy evaluation or not?
S
Yes. QNX 7.1 is based on GCC 8.
On 2020-07-23, 5:03 PM, "Development on behalf of Ville Voutilainen"
wrote:
On Thu, 23 Jul 2020 at 23:59, Thiago Macieira
wrote:
>
> On Thursday, 23 July 2020 12:34:06 PDT Simon Hausmann wrote:
> > I think the primary environment where a tran
On Fri, Jul 24, 2020 at 09:19:40AM -0400, Tristan Millns wrote:
> Take me off this list.
Every mail you get from the list has a footer, with a link to the lists
website:
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development
You can uns
Take me off this list.
> On Jul 24, 2020, at 8:56 AM, Sandro Andrade wrote:
>
> On Fri, Jul 24, 2020 at 6:58 AM Alexandru Croitor
> wrote:
>>
>>
>>
On 24. Jul 2020, at 05:59, Sandro Andrade wrote:
>>>
>>> Hi there,
>>
>> Hi!
>>
>>>
>>> I'm trying the latest Qt6 snapshot provided
On Fri, Jul 24, 2020 at 6:58 AM Alexandru Croitor
wrote:
>
>
>
> > On 24. Jul 2020, at 05:59, Sandro Andrade wrote:
> >
> > Hi there,
>
> Hi!
>
> >
> > I'm trying the latest Qt6 snapshot provided by the official installer
> > on Windows 10 with MSVC 2019.
>
> Thanks for providing feedback!
>
> >
Hi Arno,
On 7/23/20, 4:14 PM, "Arno Rehn" wrote:
I think much of the confusion stems from the fact that you can get
notifications (i.e. callbacks) without evaluating the whole binding.
From what I grok from the code, you can subscribe to "dirty" flag
changes with onValueChang
Il giorno ven 24 lug 2020 alle ore 13:18 Stottlemyer, Brett (B.S.)
ha scritto:
>
> Hi Thiago,
>
> On 7/23/20, 4:54 PM, "Development on behalf of Thiago Macieira"
>
> wrote:
>
> If a property is connected to a slot that doesn't support lazy evaluation,
> then the entire chain must be re
Il giorno gio 16 lug 2020 alle ore 10:11 Shawn Rutledge <
shawn.rutle...@qt.io> ha scritto:
>
> > On 2020 Jul 6, at 18:57, Pier Luigi Fiorini
> wrote:
> >
> > Hi,
> >
> > I noticed that some modules are going into the marketplace, for example
> Qt Multimedia.
> > Would you consider doing so for Q
On 7/23/20, 3:13 PM, "Volker Hilsheimer" wrote:
>> But why would we calculate the volume if nobody cares about the volume? :)
Stottlemyer, Brett (24 July 2020 13:45) replied:
> Qt Remote Objects. I've got a headless service on one device, and a
> remote UI for interacting with it. When signals
Hi Volker,
On 7/23/20, 3:13 PM, "Volker Hilsheimer" wrote:
But why would we calculate the volume if nobody cares about the volume? :)
Qt Remote Objects. I've got a headless service on one device, and a remote UI
for interacting with it. When signals are emitted (property change or
Hi Thiago,
On 7/23/20, 4:54 PM, "Development on behalf of Thiago Macieira"
wrote:
If a property is connected to a slot that doesn't support lazy evaluation,
then the entire chain must be re-evaluated as soon as any of the properties
is
marked dirty. QProperty needs to do that o
> On 24. Jul 2020, at 05:59, Sandro Andrade wrote:
>
> Hi there,
Hi!
>
> I'm trying the latest Qt6 snapshot provided by the official installer
> on Windows 10 with MSVC 2019.
Thanks for providing feedback!
>
> I've noticed that QMake builds work fine only in Release mode.
> Building in De
On 23/07/20 22:54, Thiago Macieira wrote:
On Thursday, 23 July 2020 12:34:06 PDT Simon Hausmann wrote:
I think the primary environment where a transition and resulting BC
breakage would be annoying is the Linux system environment with gcc. This
is where Olivier’s solution is quite elegant IMO.
21 matches
Mail list logo
