On Apr 29 2019, at 1:13 pm, Giuseppe D'Angelo via Interest
wrote:
> Hi,
>
> On 24/04/2019 21:23, Alexander Ivash wrote:
> > Yeah, it could work in theory, but in practice there already a lot of
> > places which would require such a modification. This solution just
> > doesn't scale.
>
>
> Any pre
Hi,
On 24/04/2019 21:23, Alexander Ivash wrote:
Yeah, it could work in theory, but in practice there already a lot of
places which would require such a modification. This solution just
doesn't scale.
Any preprocessing solution will require modifications at all call sites
anyhow, wouldn't it?
On 4/28/19 5:14 PM, Konstantin Tokarev wrote:
28.04.2019, 21:27, "Roland Hughes" :
On 4/28/2019 11:31 AM, Konstantin Tokarev wrote:
28.04.2019, 19:15, "Roland Hughes" :
If you are worried about a sensitive value being memory dumped because
of a completely insecure scripted language, th
28.04.2019, 21:27, "Roland Hughes" :
> On 4/28/2019 11:31 AM, Konstantin Tokarev wrote:
>> 28.04.2019, 19:15, "Roland Hughes" :
>>> If you are worried about a sensitive value being memory dumped because
>>> of a completely insecure scripted language, then don't do it there.
>> If some data is
On 4/28/2019 11:31 AM, Konstantin Tokarev wrote:
28.04.2019, 19:15, "Roland Hughes" :
If you are worried about a sensitive value being memory dumped because
of a completely insecure scripted language, then don't do it there.
If some data is copied to memory it can be dumped from there, no matt
28.04.2019, 19:15, "Roland Hughes" :
> If you are worried about a sensitive value being memory dumped because
> of a completely insecure scripted language, then don't do it there.
If some data is copied to memory it can be dumped from there, no matter
what language are you using. There are no "s
Alexander,
Having read a bit more in this thread it appears your problem isn't
syntactic, it's architectural.
Nothing sensitive should ever be done in a scripted language, period.
If you are worried about a sensitive value being memory dumped because
of a completely insecure scripted languag
Alexander,
You have brought up yet another of the limitless reasons QML and
JavaScript shouldn't be used for any production system.
Pull down this zip file.
http://www.logikalsolutions.com/wordpress/wp-content/uploads/2016/07/SerialKeypad.zip
(It's discussed in the "Raspberry Qt" post series
command before
> make, more info can be found over here:
> https://doc.qt.io/qt-5/qmake-advanced-usage.html
>
> -Original Message-
> From: Interest On Behalf Of Konstantin
> Tokarev
> Sent: April 24, 2019 3:09 PM
> To: Alexander Ivash ; interestqt-p
Konstantin Tokarev
Sent: April 24, 2019 3:09 PM
To: Alexander Ivash ; interestqt-project.org
Subject: Re: [Interest] QML preprocessing
24.04.2019, 22:01, "Alexander Ivash" :
> What I really need is some 'plugin' to qmake which would allow to
> modify qml files on the
to multiple receiver.
> > >> >
> > >> > Not sure if this would work, but maybe you can override the
> > >> console.log command into the QQmlScriptEngine and define a new
> > >> javascript function that does nothing. Maybe into the your main.cpp
> > >> whe
the rootContext() QQmlContext object, maybe you
> >> can extract the console object with QVariant contextProperty() and set the
> >> debug() property of it with a QQmlExpression, I cannot glue all this
> >> together, but maybe something into that direction could be d
you can extract the
>> console object with QVariant contextProperty() and set the debug() property
>> of it with a QQmlExpression, I cannot glue all this together, but maybe
>> something into that direction could be done before you start loading the
>> main qml file. This
is is far fetched by might work but it seem
> > overcomplicated to me.
> >
> > -Original Message-
> > From: Interest On Behalf Of Alexander
> > Ivash
> > Sent: April 24, 2019 12:56 PM
> > To: interestqt-project.org
> > Subject: [Interest] QML prepr
sh
> Sent: April 24, 2019 12:56 PM
> To: interestqt-project.org
> Subject: [Interest] QML preprocessing
>
> I understand that this topic was raised a lot of times and that this is not
> QML-way. But, what options do I have in case of requirements to eliminate all
> the loggin
-
From: Interest On Behalf Of Alexander Ivash
Sent: April 24, 2019 12:56 PM
To: interestqt-project.org
Subject: [Interest] QML preprocessing
I understand that this topic was raised a lot of times and that this is not
QML-way. But, what options do I have in case of requirements to eliminate all
the
I assume you don't use LoggingCategory.
Why?
śr., 24 kwi 2019, 18:56 użytkownik Alexander Ivash
napisał:
> I understand that this topic was raised a lot of times and that this
> is not QML-way. But, what options do I have in case of requirements to
> eliminate all the logging for release builds?
I understand that this topic was raised a lot of times and that this
is not QML-way. But, what options do I have in case of requirements to
eliminate all the logging for release builds?
Is there any hidden magic in qmake, like 'QMAKE_SUBSTITUTES' but more
flexible to substitute all the 'console.de
18 matches
Mail list logo
