Den 16-10-2014 17:39, Nuno Santos skrev:
Hi,
I’m using Slider from QtQuickControls and i’m facing a problem. I initialise
the value with a value saved on settings. However, when the slider is
instantiated, it is triggering onValueChanged with the default min value. The
setting is being
Well, yes and no. Often, when you rely on the onCompleted, this points
to a flaw in your code or design. (I said often, guys, flames not needed
:) Sometimes these checks are necessary.)
However, in your specific case, you could actually solve this without
problems:
value: settings.trackWidth
On 16 Oct 2014, at 17:39, Nuno Santos nunosan...@imaginando.pt wrote:
Hi,
I’m using Slider from QtQuickControls and i’m facing a problem. I initialise
the value with a value saved on settings. However, when the slider is
instantiated, it is triggering onValueChanged with the default
Hummm
This Settings QML type is awesome and I didn’t knew it. I had a QSettings class
exposed to QML and I was declaring all the properties I needed. This really
saves a lot of work. Should I really on it for a production product?
Regards,
Nuno
On 17 Oct 2014, at 09:43, Nurmi J-P
On 17 Oct 2014, at 10:48, Nuno Santos nunosan...@imaginando.pt wrote:
Hummm
This Settings QML type is awesome and I didn’t knew it. I had a QSettings
class exposed to QML and I was declaring all the properties I needed. This
really saves a lot of work. Should I really on it for a
Thx J-P,
I was reading Settings documentation and I have just stumbled on the following
sentence:
Writing a setting value using one instance of Settings does not update the
value in another Settings instance, even if they are referring to the same
setting in the same category.”
This is ultra
Hi,
I’m using Slider from QtQuickControls and i’m facing a problem. I initialise
the value with a value saved on settings. However, when the slider is
instantiated, it is triggering onValueChanged with the default min value. The
setting is being correctly saved because I don’t show the slider
