Hi Chris,
should individual items have to know/track this ...
Well, anchoring is also based on size changes, but uses a different type
of notification -> item change listeners.
Not sure why the authors decided to introduce yet another type of
notification - instead of using event + event filt
Hi Uwe,
On Sat, Sep 28, 2019 at 9:29 PM Uwe Rathmann wrote:
>
> On 9/28/19 8:49 AM, Simon Hausmann wrote:
>
> > Instead of an idle timer, all imperative triggered onFooChange
> > handlers are queued up and called right before the next frame.
>
> Property binding is not the only notification mecha
Hi Simon,
That sort of coalescing solves one problem, but not the other -
specifically, that if the on-change handlers are sufficiently complex,
their evaluation (and/or the evaluation of their side effects) is
likely to take longer than the time available, causing
incompletely-updated state to be
Hi Martin,
On 1/10/19 4:38 PM, Martin Koller wrote:
Hi,
I see that compiling Qt for wasm produces .a static libs.
This however leads to a couple of duplicate symbols when linking my existing
large application.
Here
https://emscripten.org/docs/compiling/Building-Projects.html?highlight=link#a
Hi,
The idea looks awesome.
This is our rough plan of how we'd like to address one aspect of QML and Qt
> Quick today. We are looking forward to any feedback and questions to help
> us review and refine this design.
>
I was wondering is there any plans to use this pattern in other Qt modules?
A
Hi,
actually, unrelated to how one can configure the stuff, at the moment,
I see still a lot of Qt internal rendering artifacts for fractional
scaling.
See https://bugreports.qt.io/browse/QTBUG-66036
For some I made now hacky workarounds in KTextEditor, see
https://bugs.kde.org/show_bug.cgi?
> On 1. Oct 2019, at 16:12, Jason H wrote:
>
>
>> I’m all for a more declarative coding style also in C++.
>> I’m wondering if we are re-inventing part of Reactive Programing a la
>> ReactiveX with QProperty, though?
>>
>> The above looks similar to (sodium-cxx):
>>
>>cell_sink surname(
> I’m all for a more declarative coding style also in C++.
> I’m wondering if we are re-inventing part of Reactive Programing a la
> ReactiveX with QProperty, though?
>
> The above looks similar to (sodium-cxx):
>
> cell_sink surname("John");
> cell_sink lastname("Smith”);
> cell fu
Am 01.10.19 um 15:18 schrieb Eike Ziller:
>
>> On 26. Sep 2019, at 17:02, Simon Hausmann wrote:
>>
>> Hi,
>>
>> Earlier this year, Olivier, Samuel, Auri and I worked on a project to
>> re-evaluate how we could bring the declarative Qt Quick approach of doing
>> user interfaces closer to C++, in
> On 26. Sep 2019, at 17:02, Simon Hausmann wrote:
>
> Hi,
>
> Earlier this year, Olivier, Samuel, Auri and I worked on a project to
> re-evaluate how we could bring the declarative Qt Quick approach of doing
> user interfaces closer to C++, in order to allow building and running user
> int
10 matches
Mail list logo
