Hi,
You’re spot on with your observation. It’s interesting to see how you ran into
the same issues back then :)
Samuel (or was it Olivier?) found a solution to that that I find very elegant
and would like to consider for QtQuick in the future: Instead of an idle timer,
all imperative triggered
Yeah that’s one way that should work for sure.
Simon
> On 26. Sep 2019, at 20:54, Thiago Macieira wrote:
>
> On Thursday, 26 September 2019 08:38:40 PDT Mitch Curtis wrote:
>> https://code.qt.io/cgit/qt/qtquickcontrols2.git/tree/src/quicktemplates2/qqu
>> ickslider.cpp#n355
>>
>> In the end
That’s a neat idea!:)
It may require additional tricks to emphasize compatibility with the underlying
type, but with a bit of luck that’s limited to qml.
Regarding failing setters: Is there another language/ environment where you
have seen this before?
The only one I can think of off the top
On Friday, 27 September 2019 10:51:00 PDT Morten Sørvig wrote:
> > The problem on that one is that you're forcing me to keep a value per each
> > individual monitor I connect to regularly. With the laptop's display
> > panel, that's 4 or 5. Since they are different actual monitors, each has
> > th
> On 27 Sep 2019, at 17:04, Thiago Macieira wrote:
>
> On Friday, 27 September 2019 03:56:44 PDT Morten Sørvig wrote:
>> Configuring Windows is a good example here: you set the slider to one of
>> 100% - 125% - 150% - 175% - 200% depending on monitor pixel density and
>> viewing distance. There
On Friday, 27 September 2019 03:56:44 PDT Morten Sørvig wrote:
> Configuring Windows is a good example here: you set the slider to one of
> 100% - 125% - 150% - 175% - 200% depending on monitor pixel density and
> viewing distance. There’s then a single value to configure.
Well, that's a good exam
While we are already at improving plugins.qmltypes, maybe we could also
enhance it a bit more and also provide a qmltypes files for all Qt basic
types and enhance the format to also allow the definition for global
objects e.g. the Qt object and its functions, which currently don't
provide any auto-
> On 26 Sep 2019, at 04:48, Thiago Macieira wrote:
>
> On Wednesday, 25 September 2019 05:54:20 PDT Morten Sørvig wrote:
>> I see two differences between setting the DPI vs a factor:
>>
>> - You set one value per screen (DPI) instead of two (DPI & factor)
>>
>> - Qt can compute the factor, ac
