Note, you can also have to add the QObject* parent on the QmlObject.
On Fri, Apr 29, 2016 at 2:34 PM, Jérôme Godbout wrote:
>
>1. You can do an Item as root object to put children. Annoying because
>it get a lot of unused properties.
>2. Or you can do your own QtObjectWithChildren fr
1. You can do an Item as root object to put children. Annoying because
it get a lot of unused properties.
2. Or you can do your own QtObjectWithChildren from C++, which is just a
QObject with children default property list of QObject*. (We did this and
call them QmlObject)
3. Or u
Thank you for your help. The syntax for creating a named object property is
what I needed.
Regards,
Viki
On 29 April 2016 at 13:12, Kristoffersen, Even (NO14) <
even.kristoffer...@honeywell.com> wrote:
> Those internal elements are not directly accessible.
>
> You can try exposing them with the
Ok Thiago, many thanks!
> On 29 Apr 2016, at 17:35, Thiago Macieira wrote:
>
> On sexta-feira, 29 de abril de 2016 17:19:03 PDT Nuno Santos wrote:
>>> So I have to ask:
>>> a) are you sure your system wasn't already hard-float?
>>
>> I don’t have a clue
>>
>>> b) if it wasn't, are the hard-fl
On sexta-feira, 29 de abril de 2016 17:19:03 PDT Nuno Santos wrote:
> > So I have to ask:
> > a) are you sure your system wasn't already hard-float?
>
> I don’t have a clue
>
> > b) if it wasn't, are the hard-float libs for EVERYTHING available on the
> >
> > system? And does the lib loader kn
2016-04-29 16:36 GMT+02:00 Jean-Michaël Celerier <
jeanmichael.celer...@gmail.com>:
>
> On Fri, Apr 29, 2016 at 1:55 PM, Ola Røer Thorsen
> wrote:
>
>>
>> float a = 1.0f;
>> float b = 2.0*a; // BAD!
>> float b = 2.0f*a; // Good!
>>
>
> Pretty sure that this would be a non-problem starting at -O1
Thiago,
> On 29 Apr 2016, at 17:12, Thiago Macieira wrote:
>
> So I have to ask:
> a) are you sure your system wasn't already hard-float?
I don’t have a clue
> b) if it wasn't, are the hard-float libs for EVERYTHING available on the
> system? And does the lib loader know how to find them?
On sexta-feira, 29 de abril de 2016 14:59:35 PDT Nuno Santos wrote:
> While Qt code may be compiled with support for hard float, the qmake.specs
> file for android doesn’t show that and, in general, it seems that hard
> float support is disabled by default in android:
Unless you're recompiling ALL
On sexta-feira, 29 de abril de 2016 13:55:05 PDT Ola Røer Thorsen wrote:
> As far as I know Qt is built with qreal as double as a default setting.
qreal is double.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
Am 26.04.16 um 22:24 schrieb Jason H:
> How I currently support English and Spanish, how do I add another language in
> Qt Linguist? it seems that I need to re-run lupdate? I'd love to be able to
> to it all by GUI, since I already have working TS files. I should be able to
> use them as the tem
On Fri, Apr 29, 2016 at 1:55 PM, Ola Røer Thorsen
wrote:
>
> float a = 1.0f;
> float b = 2.0*a; // BAD!
> float b = 2.0f*a; // Good!
>
Pretty sure that this would be a non-problem starting at -O1 optimization
level.
___
Interest mailing list
Interest@q
Ola,
Thanks for your reply.
While Qt code may be compiled with support for hard float, the qmake.specs file
for android doesn’t show that and, in general, it seems that hard float support
is disabled by default in android:
QMAKE_CFLAGS = -Wno-psabi -march=armv7-a -mfloat-abi=softfp -mfpu=vfp
On 29/04/16 15:22, Nikos Chantziaras wrote:
A statically built Qt 5.6.0 results in this when trying to run any
application built with it:
QFontDatabase: Cannot find font directory
/home/realnc/opt/qt-5.6/lib/fonts - is Qt installed correctly?
Please ignore. I'm an idiot. I forgot to pass "-fon
A statically built Qt 5.6.0 results in this when trying to run any
application built with it:
QFontDatabase: Cannot find font directory
/home/realnc/opt/qt-5.6/lib/fonts - is Qt installed correctly?
The application is completely lacking any text.
From what I was able to find, it seems I have
2016-04-29 10:11 GMT+02:00 Nuno Santos :
>
> Code compiled and ruined fine but couldn’t notice a faster performance (I
> have profiling timers in critical parts of the application).
>
> Has anyone done this before?
>
>
As far as I know Qt is built with qreal as double as a default setting.
In cas
Those internal elements are not directly accessible.
You can try exposing them with the use of alias in the root object.
-Even
From: Interest
[mailto:interest-bounces+even.kristoffersen=honeywell@qt-project.org] On
Behalf Of Viktória Nemkin
Sent: 29. april 2016 13:04
To: interest@qt-projec
Using such approach you have to write something like readonly property
QtObject backgroundColor: QtObject { ...
On Fri, Apr 29, 2016 at 2:04 PM Viktória Nemkin
wrote:
> Hello!
>
> What is a clean way to define and categorize constants in QML?
>
> I have came up with this so far:
>
> I have a QML
Hello!
What is a clean way to define and categorize constants in QML?
I have came up with this so far:
I have a QML singleton element, named Theme. There I keep a few constant
things, like different background and font colors.
Theme.qml:
pragma Singleton
import QtQuick 2.0
QtObject {
re
Hi,
I’m trying to enable hard float computation on arm.
I think I have managed to enable it doing the following changes:
1) Set a new environment var ANDROID_ARCH_TARGET=armeabi-v7a-hard
2) Adding
equals(ANDROID_TARGET_ARCH, armeabi-v7a-hard): \
QMAKE_CFLAGS = -Wno-psabi -march=armv7-a -mf
After evaluating the amount of xChanged(), yChanged() and visibleChanged()
signals I decided to stick with the approach where I create QQuickItems
from C++ with overriden updatePaintNode() instead of direct instantiation
of QSGNodes. Thank you for your help! It was tremendous useful and now I
unde
20 matches
Mail list logo
