be restricting them unnecessarily.
> Sent: Friday, July 24, 2020 at 1:45 PM
> From: "Stottlemyer, Brett (B.S.)"
> To: "Volker Hilsheimer"
> Cc: "development@qt-project.org"
> Subject: Re: [Development] QProperty and when evaluation occurs
>
>
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
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
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
Hi,
On Fri, Jul 24, 2020 at 5:17 AM Volker Hilsheimer
wrote:
> > On 23 Jul 2020, at 15:56, Stottlemyer, Brett (B.S.)
> wrote:
> >
> > Hi,
> >
> > I'm still trying to wrap my head around this concept, and starting a new
> thread to distinguish from the technical implementation discussion.
> >
>
On Thursday, 23 July 2020 12:59:25 PDT Filippo Cucchetto wrote:
> Il giorno gio 23 lug 2020 alle ore 21:15 Volker Hilsheimer
>
> ha scritto:
> > But why would we calculate the volume if nobody cares about the volume? :)
>
> Sometimes you want to notify or take actions immediately:
> - notify the
Hi Brett,
Am 23.07.2020 um 15:56 schrieb Stottlemyer, Brett (B.S.):
I'm still trying to wrap my head around this concept, and starting a new
thread to distinguish from the technical implementation discussion.
The two obvious cases:
* Immediate evaluation. This is the current signal-based hand
Il giorno gio 23 lug 2020 alle ore 21:15 Volker Hilsheimer
ha scritto:
> But why would we calculate the volume if nobody cares about the volume? :)
Sometimes you want to notify or take actions immediately:
- notify the new volume value through a websocket for being consumed
by javascript
- send
> On 23 Jul 2020, at 15:56, Stottlemyer, Brett (B.S.) wrote:
>
> Hi,
>
> I'm still trying to wrap my head around this concept, and starting a new
> thread to distinguish from the technical implementation discussion.
>
> The two obvious cases:
> * Immediate evaluation. This is the current sign
Hi Brett,
if I understood correctly what you wrote you're basically asking how
to handle the scenario of an observer of a QProperty (given that it
recomputes its value only if someone reads it).
By your example i would assume that basically you can achieve what you
want with a QTimer(0) that re/rea
Hi,
I'm still trying to wrap my head around this concept, and starting a new thread
to distinguish from the technical implementation discussion.
The two obvious cases:
* Immediate evaluation. This is the current signal-based handling (ignoring
queued for the moment).
* Evaluate-on-Read (EoR).
14 matches
Mail list logo
