Re: [Interest] L Word

[Filip Piechocki]

I totally agree with you, Guiseppe.

I am subscribed to this list for a long time as it happened several times
in the past that the issues I was facing with Qt were already solved here.
But the list became more of a Roland's trolling sandbox, where he is
throwing sand in others' eyes and having great fun of that, with less and
less useful content in this list over time. I think that more and more
people get tired of those endless rants and just go somewhere else.

So do I.

F

On Thu, Apr 29, 2021 at 10:27 AM Giuseppe D'Angelo via Interest <
interest@qt-project.org> wrote:

> On 29/04/2021 00:42, Giuseppe D'Angelo via Interest wrote:
> > If the answer is yes, you were lying. If the answer is no, or you don't
> > answer, then you're trolling the mailing list. You'll get my apology;
> > I'll even throw in, for free, my personal congratulations for the long
> > trolling. But, you'll get a nice permanent ban from here.
>
> No reply. Yes, you're not the only one who can set arbitrary deadlines
> for other people, pal.
>
>
> I'll just go with the script then: you DID believe those links to be true.
>
> Then, please accept my deepest and most sincere apologies for calling
> you a liar.
>
> I'll state it again, very clearly, all uppercase:
>
> YOU NEVER LIED. I WAS WRONG.
>
> Please accept the attached fruit basket as a gesture of good will.
>
> ===
>
> Where does this leave us, then?
>
> At BEST, you have been trolling the mailing list, sending inflammatory
> false content with the purpose of getting a strong reaction from the
> participants.
>
> At WORST, you have demonstrated some abysmal gross incompetence, since
> in order to win an argument you:
>
> * googled some keywords;
> * got the first couple of links that seemed to match your thesis;
> * didn't even bother to read the contents;
> * pasted the links here believing they were true, without questioning
> the veracity of such explosive statements;
> * when busted, dug your hole even deeper by keeping arguing in that
> direction.
>
> (...I'm not alone about bringing this possibility forward...)
>
> Spoiler alert, the links were April fools' jokes. They have never been
> true, and it was even written in the articles that they were jokes. With
> such precedents, why should anyone believe *any* other argument you
> bring forward?
>
> ===
>
> In either case, it is abundantly clear who's full of shit around here.
>
> It is also clear to me that moderation on this list doesn't exist, or if
> it exists, it doesn't want to get sides, and/or considers these
> behaviours acceptable.
>
> I don't. And I don't send ultimatums or threats of libel lawsuits
> (seriously?) around, including to the moderators, in order to force them
> to make a move.
>
> Hence, I'll be removing myself from this list, effective immediately.
>
>
> You win. Audience claps. Curtains.
>
> Ad astra per aspera,
> --
> Giuseppe D'Angelo | giuseppe.dang...@kdab.com | Senior Software Engineer
> KDAB (France) S.A.S., a KDAB Group company
> Tel. France +33 (0)4 90 84 08 53, http://www.kdab.com
> KDAB - The Qt, C++ and OpenGL Experts
>
> ___
> Interest mailing list
> Interest@qt-project.org
> https://lists.qt-project.org/listinfo/interest
>
___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest

Re: [Interest] [Development] Windows 7 support will be dropped in Qt 6

[Filip Piechocki]

Hi,
for me not updating a system, software etc for many years is just equal to
building a technical debt. Any serious company should be aware that this
will finally kick them in their butt, should have measure the potential
cost and decide where is the point where they should switch. If a company
decides to not care about this then someone else will decide for them for
example by dropping support for their OS/hardware/whatever.
Backwards compatibility is nice but the world (especially IT world) is
moving forward and lagging behind is a potential risk and cost.

BR
Filip

On Sat, Jun 13, 2020, 09:21 Konrad Rosenbaum  wrote:

> On 2020-06-12 02:44, Hamish Moffatt wrote:
> > On 12/6/20 10:17 am, Scott Bloom wrote:
> >> Why is Win7 being dropped?  I (my company) has gotten burned pretty
> >> hard by the dropping of CentOS 6, similar reasons listed for win7..
> >
> > It's funny that there's so much discussion about dropping Windows 7
> > which was released 11 years ago.
> >
> > Yet Qt 5.15 already dropped macOS prior to 10.13, which is not even 3
> > years old. And Qt trunk requires 10.14, which is only 2 years old.
> > This is really a major PITA.
>
>
> From an industry perspective: I have seen lots of machines running all
> kinds of outdated versions of Windows(*) or rather old versions of
> RedHat or embedded Linux(**), but it has been a very very long time
> since I have seen a machine running some Apple product of any version.
> I.e. there are plenty of Windows users who have the bucks to demand long
> term support for their systems, the same cannot be said for Apple users.
>
> (*)if you walk into a running factory it is pretty normal to find a
> large portion of the machines running XP, I would not be surprised to
> find a W2k machine or even a machine running DOS in a factory that has
> been running for 15 years. New factories will have plenty of machines
> running Win7, because new OSes is simply not what the machine suppliers
> care about most.
>
> (**)you will regularly find machines running a 2.6 kernel, some may even
> run 2.4. Many GUIs look suspiciously Motif-like and if you get to see
> the window manager behind the full-screen GUI it may look eerily CDE-ish
> or FVWM-like.
>
> Industry is willing to pay large amounts of support and maintenance
> costs for the machines they run - this is what keeps people like Roland
> and me well fed. Unless you can find a large industry or two that care
> about legacy MacOS and are willing to pay tons of money for support, it
> will stay bleeding edge because maintenance cost goes up exponentially
> with the number of systems you have to support.
>
>
>
> Konrad
>
>
> ___
> Interest mailing list
> Interest@qt-project.org
> https://lists.qt-project.org/listinfo/interest
>
___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest

Re: [Interest] Official builds configuration options

[Filip Piechocki]

That does not seem right as Qt 5.12.0 for Android is built with clang
and those configure lines have:
-xplatform android-g++

BR,
Filip Piechocki

On Thu, Jan 24, 2019 at 11:11 AM Konstantin Podsvirov
 wrote:
>
>
>
> 12:55, 24 January 2019 г., Filip Piechocki :
>
> Thanks, but cannot find that there :(
>
> Look there:
>
> http://code.qt.io/cgit/qtsdk/qtsdk.git/tree/packaging-tools/bld_config
>
> configure_android_armv7_opensource:
>
> -opensource -confirm-license -release -xplatform android-g++ -opengl es2 
> -android-arch armeabi-v7a -nomake tests -nomake examples -skip qtserialport 
> -skip qtwebkit -skip qtwebkit-examples -skip qtx11extras -sysconfdir /etc/xdg 
> -no-icu -openssl
>
>
> configure_android_armv7_enterpris:
>
> -commercial -confirm-license -release -xplatform android-g++ -opengl es2 
> -android-arch armeabi-v7a -nomake tests -nomake examples -skip qtserialport 
> -skip qtwebkit -skip qtwebkit-examples -skip qtx11extras -sysconfdir /etc/xdg 
> -no-icu -openssl
>
> BR,
> Filip Piechocki
>
> On Thu, Jan 24, 2019 at 10:31 AM Konstantin Podsvirov
>  wrote:
>
>  Hello Filip!
>
>  Try look there:
>
>  http://code.qt.io/cgit/qtsdk/qtsdk.git
>
>  12:20, 24 January 2019 г., Filip Piechocki :
>
>  Hi,
>  Where can I find official builds (available from Qt Maintenance Tool)
>  configure options? I am especially interested in Qt 5.12.0 for Android
>  armv7 build.
>
>  Best regards,
>  Filip Piechocki
>  ___
>  Interest mailing list
>  Interest@qt-project.org
>  https://lists.qt-project.org/listinfo/interest
>
>
>  Regards,
>  Konstantin Podsvirov
___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest

[Interest] Official builds configuration options

[Filip Piechocki]

Hi,
Where can I find official builds (available from Qt Maintenance Tool)
configure options? I am especially interested in Qt 5.12.0 for Android
armv7 build.

Best regards,
Filip Piechocki
___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest

Re: [Interest] Android NDK with clang for 5.12.0?

[Filip Piechocki]

Didn;t even know that QtCreator can detect NDK and so on as it is
quite simple to add proper Clang and its -target switch (look at
qmake.conf in android-clang mkspec) together with Qt for Android built
with this clang and setup new Kit. It works :)

BR
Filip

On Tue, Dec 18, 2018 at 1:54 PM René Hansen  wrote:
>
> I think I'd run into one of those spurious QtCreator flakes, so I just nuked 
> everything; all settings etc. and started over. It seems to correctly detect 
> the NDK now.
>
> Thanks again,
>
> /René
>
> On Tue, 18 Dec 2018 at 12:34 ekke  wrote:
>>
>> Hi René,
>>
>> Android NDK r18b should work with Qt 5.12.0 and detect clang.
>> (on macOS 10.13.6)
>> Build / Target SDK 28
>>
>> ekke
>>
>> Am 18.12.18 um 12:08 schrieb René Hansen:
>>
>> Hi all,
>>
>>
>> So I'm finally trying to make the jump from 5.11 to 5.12 and also upgrade 
>> from ndk r10e, but I've yet to get the setup correct.
>>
>> This says to just use the "latest" with android-clang toolchain, but not 
>> much else.
>>
>> http://doc.qt.io/qt-5/android-getting-started.html
>>
>> However, just updating Android NDK Location, to point to e.g. r16b doesn't 
>> seem to work. I keep getting:
>>
>> "No compiler can produce code for this Qt version. Please define one or more 
>> compilers for:"
>>
>> I've tried r18b as well.
>>
>> Has anyone else successfully gotten this to work?
>>
>>
>> /René
>>
>> ___
>> Interest mailing list
>> Interest@qt-project.org
>> https://lists.qt-project.org/listinfo/interest
>>
>> ___
>> Interest mailing list
>> Interest@qt-project.org
>> https://lists.qt-project.org/listinfo/interest
>
> ___
> Interest mailing list
> Interest@qt-project.org
> https://lists.qt-project.org/listinfo/interest
___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest

Re: [Interest] Android NDK with clang for 5.12.0?

[Filip Piechocki]

Oops, forgot to mention that we are using NDK 18

On Tue, Dec 18, 2018 at 12:29 PM Filip Piechocki  wrote:
>
> Hi,
> Yes, we are building Qt 5.12.0 and 5.11.2 with android-clang with NDK
> installed via Android SDK (or Android Studio) so the location is
> /opt/Android/ndk-bundle. Here is my configure line from building Qt
> 5.12.0-rc:
> ./configure -opensource -confirm-license -prefix
> /opt/qt/5.12-rc-android-clang -xplatform android-clang -make libs
> -android-sdk /opt/Android -android-ndk /opt/Android/ndk-bundle
> -android-ndk-host linux-x86_64 -android-toolchain-version 4.9
> -android-arch armeabi-v7a -android-ndk-platform android-24
>
> BR,
> Filip
>
> On Tue, Dec 18, 2018 at 12:23 PM René Hansen  wrote:
> >
> > Hi all,
> >
> >
> > So I'm finally trying to make the jump from 5.11 to 5.12 and also upgrade 
> > from ndk r10e, but I've yet to get the setup correct.
> >
> > This says to just use the "latest" with android-clang toolchain, but not 
> > much else.
> >
> > http://doc.qt.io/qt-5/android-getting-started.html
> >
> > However, just updating Android NDK Location, to point to e.g. r16b doesn't 
> > seem to work. I keep getting:
> >
> > "No compiler can produce code for this Qt version. Please define one or 
> > more compilers for:"
> >
> > I've tried r18b as well.
> >
> > Has anyone else successfully gotten this to work?
> >
> >
> > /René
> > ___
> > Interest mailing list
> > Interest@qt-project.org
> > https://lists.qt-project.org/listinfo/interest
___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest

Re: [Interest] Android NDK with clang for 5.12.0?

[Filip Piechocki]

Hi,
Yes, we are building Qt 5.12.0 and 5.11.2 with android-clang with NDK
installed via Android SDK (or Android Studio) so the location is
/opt/Android/ndk-bundle. Here is my configure line from building Qt
5.12.0-rc:
./configure -opensource -confirm-license -prefix
/opt/qt/5.12-rc-android-clang -xplatform android-clang -make libs
-android-sdk /opt/Android -android-ndk /opt/Android/ndk-bundle
-android-ndk-host linux-x86_64 -android-toolchain-version 4.9
-android-arch armeabi-v7a -android-ndk-platform android-24

BR,
Filip

On Tue, Dec 18, 2018 at 12:23 PM René Hansen  wrote:
>
> Hi all,
>
>
> So I'm finally trying to make the jump from 5.11 to 5.12 and also upgrade 
> from ndk r10e, but I've yet to get the setup correct.
>
> This says to just use the "latest" with android-clang toolchain, but not much 
> else.
>
> http://doc.qt.io/qt-5/android-getting-started.html
>
> However, just updating Android NDK Location, to point to e.g. r16b doesn't 
> seem to work. I keep getting:
>
> "No compiler can produce code for this Qt version. Please define one or more 
> compilers for:"
>
> I've tried r18b as well.
>
> Has anyone else successfully gotten this to work?
>
>
> /René
> ___
> Interest mailing list
> Interest@qt-project.org
> https://lists.qt-project.org/listinfo/interest
___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest

[Interest] Android service starting on boot

[Filip Piechocki]

Hi,
I would like to create an Android service with Qt that will start at
boot. The thing is that all the information I've found says how to
create a service that is an addition to activity while I would like to
have the service part only. Basing on this tutorial on KDAB page
(https://www.kdab.com/qt-android-create-android-service-using-qt/) I
was able to create an apk with activity (app showing a simple QtQuick
window) and a service which was able to start at boot. Then I've just
removed the  section from manifest and it builds and
installs but nothing happens on boot.
Basically the motivation is to have some C++ with Qt services that are
now happily running as systemd services to be able to wrap them as
Android services.
Has anyone tried that?

Best Regards,
Filip
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

[Interest] Mouse as touch

[Filip Piechocki]

Hi,
I have two similar devices with the only significant difference in touch
screens - one is resistive and the other capacitive. I'm running linux with
X11 and need to show fullscreen web content in WebEngineView. The thing is
that this resistive touch screen produces mouse events so trying to click a
hiper link triggers drag and drop and it is impossible to scroll a page by
swiping (it is text selection). How can I tell WebEngineView to treat a
mouse like touch?

BR,
Filip
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] QML vs Electron

[Filip Piechocki]

Hi,
recently I was comparing animation performance on i.MX6 DualLite SoC
between QtQuick and HTML. I'm not an expert in HTML so do not know if I did
things best possible way, but I took Servo rendering benchmark (
https://youtu.be/u0hYIRQRiws there is a link in a description) an reduced
number of elements to 60 to get sane results on such weak ARM device I
have. Then I reimplemented this in QtQuick. So the results are 8fps for
HTML and 60fps for QtQuick.

QML/QtQuick is quite easy and sometimes you'll be surprised that you
could've create what you wanted in such few lines of code. But on the other
hand, there are things that are not obvious, Qt docs can be lacking some
details on something and you may come up with something that looks like
hack rather than proper solution.

Last but not least - QML is declarative and it is hard to switch from C++.
I saw qml files filled with walls of imperative JavaScript code, like some
filtering done by copying elements from one ListModel to the other instead
of proper proxy model in c++, state handling by ifs spaghetti and some
properties like "stateOne: 1" etc. I always suggest getting some
professional QtQuick training if that is possible to avoid common mistakes.

BR
Filip

On Feb 15, 2018 5:36 AM, "Jason H"  wrote:

> > > Anyway, you can lament it, but that ship has sailed.
> > > If you really want to know what I'm thinking, it would be to ditch JS
> entirely and use ChaiScript in QML.
> >
> >
> > Thanks for the response, Jason.
> >
> > If I understand your salient point here, you're advocating the
> "traditional"
> > approach of just maintaining device-specific, not-necessarily-related
> code
> > bases that duplicate the same application functionality?  So, use the
> > per-platform accepted coding frameworks -- C# for Android, ObjC for iOS,
> Qt
> > for dekstops, etc. -- and just develop the required expertise in each
> area?
>
> Not at all. Just the loftiness of Widgets everywhere is unlikely to ever
> be realized. Qt does a lot very well. I've heard lamenting that most people
> get QML wrong - that JS is not to be the application code, just the glue
> code. There certainly is appeal to that, C++ code is the most portable and
> most efficient, but in the end it is easier to just write JS instead of
> C++, though ChaiScript would bridge that gap. JS also bring in async issues
> and its own event loop.
>
> Anyway, at the end of the day, Qt is a success, and the intricacies of
> dealing with the various platforms is made manageable. I just assume there
> is no back button on the device. Android users never complain.
>
> ___
> Interest mailing list
> Interest@qt-project.org
> http://lists.qt-project.org/mailman/listinfo/interest
>
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] Cannot complie Qt 5.10 on ARM device

[Filip Piechocki]

I am running this in a docker container (iamge:
arm32v7/debian:buster). It is done on Asus Tinker board with kernel
version 4.4.71.

On Thu, Jan 11, 2018 at 3:53 PM, Thiago Macieira
<thiago.macie...@intel.com> wrote:
> On Friday, 22 December 2017 04:31:34 PST Filip Piechocki wrote:
>> Could not find qmake configuration file .
>
> qmake failing to find files inn 5.10 could be related to a new system call
> that we're using on Linux. Can you confirm which kernel version you're running
> with? Do you have any type of system call filtering active? For example, by
> using a container or something.
>
> --
> Thiago Macieira - thiago.macieira (AT) intel.com
>   Software Architect - Intel Open Source Technology Center
>
> ___
> Interest mailing list
> Interest@qt-project.org
> http://lists.qt-project.org/mailman/listinfo/interest
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] Cannot complie Qt 5.10 on ARM device

[Filip Piechocki]

Anyone has an idea on what is wrong here?

On Fri, Dec 22, 2017 at 1:31 PM, Filip Piechocki <fpiecho...@gmail.com> wrote:
> Hi,
> I am now trying to build Qt 5.10 on i.MX6 device (cross compiling is
> not an option at this moment). I've prepared my custom mkspec called
> linux-imx6-g++ and I put it in qtbase/mkspecs directory. This works
> perfectly fine with Qt 5.9.1 and Qt 5.9.3 while with Qt 5.10.0 I get:
>
> Could not find qmake configuration file .
>
> no matter what I options do I use with configure (so with or without
> my custom mkspec). Here is output of qtbase/bin/qmake -query for Qt
> 5.10:
>
> root@linaro-alip:~/qt-everywhere-src-5.10.0# qtbase/bin/qmake -query
> QT_SYSROOT:
> QT_INSTALL_PREFIX:/root/qt-everywhere-src-5.10.0/qtbase/bin
> QT_INSTALL_ARCHDATA:/root/qt-everywhere-src-5.10.0/qtbase/bin
> QT_INSTALL_DATA:/root/qt-everywhere-src-5.10.0/qtbase/bin
> QT_INSTALL_DOCS:/root/qt-everywhere-src-5.10.0/qtbase/bin/doc
> QT_INSTALL_HEADERS:/root/qt-everywhere-src-5.10.0/qtbase/bin/include
> QT_INSTALL_LIBS:/root/qt-everywhere-src-5.10.0/qtbase/bin/lib
> QT_INSTALL_LIBEXECS:/root/qt-everywhere-src-5.10.0/qtbase/bin/libexec
> QT_INSTALL_BINS:/root/qt-everywhere-src-5.10.0/qtbase/bin/bin
> QT_INSTALL_TESTS:/root/qt-everywhere-src-5.10.0/qtbase/bin/tests
> QT_INSTALL_PLUGINS:/root/qt-everywhere-src-5.10.0/qtbase/bin/plugins
> QT_INSTALL_IMPORTS:/root/qt-everywhere-src-5.10.0/qtbase/bin/imports
> QT_INSTALL_QML:/root/qt-everywhere-src-5.10.0/qtbase/bin/qml
> QT_INSTALL_TRANSLATIONS:/root/qt-everywhere-src-5.10.0/qtbase/bin/translations
> QT_INSTALL_CONFIGURATION:/root/qt-everywhere-src-5.10.0/qtbase/bin
> QT_INSTALL_EXAMPLES:/root/qt-everywhere-src-5.10.0/qtbase/bin/examples
> QT_INSTALL_DEMOS:/root/qt-everywhere-src-5.10.0/qtbase/bin/examples
> QT_HOST_PREFIX:/root/qt-everywhere-src-5.10.0/qtbase/bin
> QT_HOST_DATA:/root/qt-everywhere-src-5.10.0/qtbase/bin
> QT_HOST_BINS:/root/qt-everywhere-src-5.10.0/qtbase/bin/bin
> QT_HOST_LIBS:/root/qt-everywhere-src-5.10.0/qtbase/bin/lib
> QMAKE_SPEC:
> QMAKE_XSPEC:
> QMAKE_VERSION:3.1
> QT_VERSION:5.10.0
>
> and now Qt 5.9.3 for comparison:
> root@linaro-alip:~/qt-everywhere-opensource-src-5.9.3# qtbase/bin/qmake -query
> QMAKE_SPEC:linux-imx6-native-g++
> QT_SYSROOT:
> QT_INSTALL_PREFIX:/usr
> QT_INSTALL_PREFIX/get:/root/qt-everywhere-opensource-src-5.9.3/qtbase
> QT_INSTALL_ARCHDATA:/usr
> QT_INSTALL_ARCHDATA/get:/root/qt-everywhere-opensource-src-5.9.3/qtbase
> QT_INSTALL_DATA:/usr
> QT_INSTALL_DATA/get:/root/qt-everywhere-opensource-src-5.9.3/qtbase
> QT_INSTALL_DOCS:/usr/doc
> QT_INSTALL_DOCS/get:/root/qt-everywhere-opensource-src-5.9.3/qtbase/doc
> QT_INSTALL_HEADERS:/usr/include
> QT_INSTALL_HEADERS/get:/root/qt-everywhere-opensource-src-5.9.3/qtbase/include
> QT_INSTALL_LIBS:/usr/lib
> QT_INSTALL_LIBS/get:/root/qt-everywhere-opensource-src-5.9.3/qtbase/lib
> QT_INSTALL_LIBEXECS:/usr/libexec
> QT_INSTALL_LIBEXECS/get:/root/qt-everywhere-opensource-src-5.9.3/qtbase/libexec
> QT_INSTALL_BINS:/usr/bin
> QT_INSTALL_BINS/get:/root/qt-everywhere-opensource-src-5.9.3/qtbase/bin
> QT_INSTALL_TESTS:/usr/tests
> QT_INSTALL_TESTS/get:/root/qt-everywhere-opensource-src-5.9.3/qtbase/tests
> QT_INSTALL_PLUGINS:/usr/plugins
> QT_INSTALL_PLUGINS/get:/root/qt-everywhere-opensource-src-5.9.3/qtbase/plugins
> QT_INSTALL_IMPORTS:/usr/imports
> QT_INSTALL_IMPORTS/get:/root/qt-everywhere-opensource-src-5.9.3/qtbase/imports
> QT_INSTALL_QML:/usr/qml
> QT_INSTALL_QML/get:/root/qt-everywhere-opensource-src-5.9.3/qtbase/qml
> QT_INSTALL_TRANSLATIONS:/usr/translations
> QT_INSTALL_TRANSLATIONS/get:/root/qt-everywhere-opensource-src-5.9.3/qtbase/translations
> QT_INSTALL_CONFIGURATION:/usr
> QT_INSTALL_CONFIGURATION/get:/root/qt-everywhere-opensource-src-5.9.3/qtbase
> QT_INSTALL_EXAMPLES:/usr/examples
> QT_INSTALL_EXAMPLES/get:/root/qt-everywhere-opensource-src-5.9.3/qtbase/examples
> QT_INSTALL_DEMOS:/usr/examples
> QT_INSTALL_DEMOS/get:/root/qt-everywhere-opensource-src-5.9.3/qtbase/examples
> QT_HOST_PREFIX:/usr
> QT_HOST_PREFIX/get:/root/qt-everywhere-opensource-src-5.9.3/qtbase
> QT_HOST_DATA:/usr
> QT_HOST_DATA/get:/root/qt-everywhere-opensource-src-5.9.3/qtbase
> QT_HOST_BINS:/usr/bin
> QT_HOST_BINS/get:/root/qt-everywhere-opensource-src-5.9.3/qtbase/bin
> QT_HOST_LIBS:/usr/lib
> QT_HOST_LIBS/get:/root/qt-everywhere-opensource-src-5.9.3/qtbase/lib
> QMAKE_SPEC:linux-imx6-g++
> QMAKE_XSPEC:linux-imx6-g++
> QMAKE_VERSION:3.1
> QT_VERSION:5.9.3
>
> what should I do now to be able to build Qt 5.10?
>
> BR,
> Filip Piechocki
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

[Interest] Cannot complie Qt 5.10 on ARM device

[Filip Piechocki]

Hi,
I am now trying to build Qt 5.10 on i.MX6 device (cross compiling is
not an option at this moment). I've prepared my custom mkspec called
linux-imx6-g++ and I put it in qtbase/mkspecs directory. This works
perfectly fine with Qt 5.9.1 and Qt 5.9.3 while with Qt 5.10.0 I get:

Could not find qmake configuration file .

no matter what I options do I use with configure (so with or without
my custom mkspec). Here is output of qtbase/bin/qmake -query for Qt
5.10:

root@linaro-alip:~/qt-everywhere-src-5.10.0# qtbase/bin/qmake -query
QT_SYSROOT:
QT_INSTALL_PREFIX:/root/qt-everywhere-src-5.10.0/qtbase/bin
QT_INSTALL_ARCHDATA:/root/qt-everywhere-src-5.10.0/qtbase/bin
QT_INSTALL_DATA:/root/qt-everywhere-src-5.10.0/qtbase/bin
QT_INSTALL_DOCS:/root/qt-everywhere-src-5.10.0/qtbase/bin/doc
QT_INSTALL_HEADERS:/root/qt-everywhere-src-5.10.0/qtbase/bin/include
QT_INSTALL_LIBS:/root/qt-everywhere-src-5.10.0/qtbase/bin/lib
QT_INSTALL_LIBEXECS:/root/qt-everywhere-src-5.10.0/qtbase/bin/libexec
QT_INSTALL_BINS:/root/qt-everywhere-src-5.10.0/qtbase/bin/bin
QT_INSTALL_TESTS:/root/qt-everywhere-src-5.10.0/qtbase/bin/tests
QT_INSTALL_PLUGINS:/root/qt-everywhere-src-5.10.0/qtbase/bin/plugins
QT_INSTALL_IMPORTS:/root/qt-everywhere-src-5.10.0/qtbase/bin/imports
QT_INSTALL_QML:/root/qt-everywhere-src-5.10.0/qtbase/bin/qml
QT_INSTALL_TRANSLATIONS:/root/qt-everywhere-src-5.10.0/qtbase/bin/translations
QT_INSTALL_CONFIGURATION:/root/qt-everywhere-src-5.10.0/qtbase/bin
QT_INSTALL_EXAMPLES:/root/qt-everywhere-src-5.10.0/qtbase/bin/examples
QT_INSTALL_DEMOS:/root/qt-everywhere-src-5.10.0/qtbase/bin/examples
QT_HOST_PREFIX:/root/qt-everywhere-src-5.10.0/qtbase/bin
QT_HOST_DATA:/root/qt-everywhere-src-5.10.0/qtbase/bin
QT_HOST_BINS:/root/qt-everywhere-src-5.10.0/qtbase/bin/bin
QT_HOST_LIBS:/root/qt-everywhere-src-5.10.0/qtbase/bin/lib
QMAKE_SPEC:
QMAKE_XSPEC:
QMAKE_VERSION:3.1
QT_VERSION:5.10.0

and now Qt 5.9.3 for comparison:
root@linaro-alip:~/qt-everywhere-opensource-src-5.9.3# qtbase/bin/qmake -query
QMAKE_SPEC:linux-imx6-native-g++
QT_SYSROOT:
QT_INSTALL_PREFIX:/usr
QT_INSTALL_PREFIX/get:/root/qt-everywhere-opensource-src-5.9.3/qtbase
QT_INSTALL_ARCHDATA:/usr
QT_INSTALL_ARCHDATA/get:/root/qt-everywhere-opensource-src-5.9.3/qtbase
QT_INSTALL_DATA:/usr
QT_INSTALL_DATA/get:/root/qt-everywhere-opensource-src-5.9.3/qtbase
QT_INSTALL_DOCS:/usr/doc
QT_INSTALL_DOCS/get:/root/qt-everywhere-opensource-src-5.9.3/qtbase/doc
QT_INSTALL_HEADERS:/usr/include
QT_INSTALL_HEADERS/get:/root/qt-everywhere-opensource-src-5.9.3/qtbase/include
QT_INSTALL_LIBS:/usr/lib
QT_INSTALL_LIBS/get:/root/qt-everywhere-opensource-src-5.9.3/qtbase/lib
QT_INSTALL_LIBEXECS:/usr/libexec
QT_INSTALL_LIBEXECS/get:/root/qt-everywhere-opensource-src-5.9.3/qtbase/libexec
QT_INSTALL_BINS:/usr/bin
QT_INSTALL_BINS/get:/root/qt-everywhere-opensource-src-5.9.3/qtbase/bin
QT_INSTALL_TESTS:/usr/tests
QT_INSTALL_TESTS/get:/root/qt-everywhere-opensource-src-5.9.3/qtbase/tests
QT_INSTALL_PLUGINS:/usr/plugins
QT_INSTALL_PLUGINS/get:/root/qt-everywhere-opensource-src-5.9.3/qtbase/plugins
QT_INSTALL_IMPORTS:/usr/imports
QT_INSTALL_IMPORTS/get:/root/qt-everywhere-opensource-src-5.9.3/qtbase/imports
QT_INSTALL_QML:/usr/qml
QT_INSTALL_QML/get:/root/qt-everywhere-opensource-src-5.9.3/qtbase/qml
QT_INSTALL_TRANSLATIONS:/usr/translations
QT_INSTALL_TRANSLATIONS/get:/root/qt-everywhere-opensource-src-5.9.3/qtbase/translations
QT_INSTALL_CONFIGURATION:/usr
QT_INSTALL_CONFIGURATION/get:/root/qt-everywhere-opensource-src-5.9.3/qtbase
QT_INSTALL_EXAMPLES:/usr/examples
QT_INSTALL_EXAMPLES/get:/root/qt-everywhere-opensource-src-5.9.3/qtbase/examples
QT_INSTALL_DEMOS:/usr/examples
QT_INSTALL_DEMOS/get:/root/qt-everywhere-opensource-src-5.9.3/qtbase/examples
QT_HOST_PREFIX:/usr
QT_HOST_PREFIX/get:/root/qt-everywhere-opensource-src-5.9.3/qtbase
QT_HOST_DATA:/usr
QT_HOST_DATA/get:/root/qt-everywhere-opensource-src-5.9.3/qtbase
QT_HOST_BINS:/usr/bin
QT_HOST_BINS/get:/root/qt-everywhere-opensource-src-5.9.3/qtbase/bin
QT_HOST_LIBS:/usr/lib
QT_HOST_LIBS/get:/root/qt-everywhere-opensource-src-5.9.3/qtbase/lib
QMAKE_SPEC:linux-imx6-g++
QMAKE_XSPEC:linux-imx6-g++
QMAKE_VERSION:3.1
QT_VERSION:5.9.3

what should I do now to be able to build Qt 5.10?

BR,
Filip Piechocki
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] QtMqtt

[Filip Piechocki]

Hi,
Was playing a bit with QtMqtt and written some example publisher that
shares files from a specific directory. Each file contents is sent as a one
message on /dirName/fileName topic so a subscriber subscribes on /dirName/+

Along the files there was an 35MB mp4 file (so way below MQTT's ~256MB
limit). And it was not sent. I've debugged this and the cause seems to be
data.constData() in QMqttControlPacket::appendRaw() - m_payload.size() does
not change after append while it was appending 35MB bytearray. Removing
.constData() solves the issue - data is properly appended to payload and
subscriber got this message. Is there any reason for constData() there?
Same in append() - also constData is used there.

Another thing is that QMqttConnection::writePacketToTransport() checks if
_any_ bytes were written to QIODevice and what about case where actually
written byte count is _less_ than what we wanted to write?

BR,
Filip

On Oct 10, 2017 09:35, "Maurice Kalinowski" <maurice.kalinow...@qt.io>
wrote:

> Hi,
>
> Only with limited network right now, but the repo has been opened
> yesterday evening and you can find it here
> https://codereview.qt-project.org/#/admin/projects/qt/
> <https://codereview.qt-project.org/#/admin/projects/qt/qtmqtt>qtmqtt
> <https://codereview.qt-project.org/#/admin/projects/qt/qtmqtt>
>
> Also jira has a component for it.
>
> Be,
> Maurice
>
>
> Outlook for Android <https://aka.ms/ghei36> herunterladen
>
> --
> *From:* Filip Piechocki <fpiecho...@gmail.com>
> *Sent:* Tuesday, October 10, 2017 8:34:07 AM
> *To:* Maurice Kalinowski
> *Cc:* interest@qt-project.org Interest
> *Subject:* Re: [Interest] QtMqtt
>
> Hi,
> so how is it going? QtWS starts today, QtMqtt was mentioned in Qt 5.10
> beta release yesterday but I cannot find it anywhere...
>
> BR,
> Filip
>
> On Mon, Sep 25, 2017 at 11:05 AM, Maurice Kalinowski <
> maurice.kalinow...@qt.io> wrote:
>
>> Hi Filip,
>>
>>
>>
>> I’m afraid to say “not yet”. We’ve been struggling with getting the
>> infrastructure in place (with positive updates over the weekend). Currently
>> there are logistical items to be done (license header updates, etc.), but
>> we are progressing nicely now.
>>
>>
>>
>> The aim is to have everything available (also Qt Knx) within the Qt World
>> Summit timeframe. Probably, or hopefully, earlier.
>>
>>
>>
>> BR,
>>
>> Maurice
>>
>>
>>
>>
>>
>> *From:* Interest [mailto:interest-bounces+maurice.kalinowski=
>> qt...@qt-project.org] *On Behalf Of *Filip Piechocki
>> *Sent:* Friday, September 22, 2017 3:10 PM
>> *To:* interest@qt-project.org Interest <interest@qt-project.org>
>> *Subject:* [Interest] QtMqtt
>>
>>
>>
>> Hi,
>>
>> It's been over a month since the QtMqtt blog post (
>> http://blog.qt.io/blog/2017/08/14/introducing-qtmqtt-protocol/) but I
>> can't find the code to download. Is it already available somewhere?
>>
>>
>>
>> Best regards,
>>
>> Filip Piechocki
>>
>
>
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

[Interest] Qt 5.9.1 for Android 4.0

[Filip Piechocki]

Hi,
I would like to use Qt 5.9.1 on Android 4.0 but docs say that at least
Android 4.1 is required. Is there any workaround for that? Like for example
some module requires it and we can just not use it in our deployment? What
in Qt 5.9.1 requires API level 16?

BR,
Filip
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] Interest Digest Wiki instructions for PI cross compile do not work for PostgreSQL support

[Filip Piechocki]

On Oct 20, 2017 00:11, "Roland Hughes" <rol...@logikalsolutions.com> wrote:

It's not misleading when it is a hog fattened way past market.

90% of the embedded systems I encounter have no GPU so the driver issue is
irrelevant. You get rid of all needless things to improve battery life.
Claiming an i.MX6 which most certainly must need grid power or batteries
the size of a house is the "normal" embedded processor for medical devices
or industrial control is simply ludicrous.

And how much of embedded market are devices you are talking about? 5%? 1%?
0.1%?

90% of embedded devices I encounter DO have GPU and these are TVs, set top
boxes, phones, public transport systems and even fridge. Oh, and using HW
parts that are specifically designed for some things (like GPUs are for
graphics) often gives much higher performance/(power draw). Of course it
depends how much you will use it.

I was using a Pi-II not a 1. The Pi-II has wy more
horsepower than the vast majority of embedded systems I'm talking about.

But it is still very weak CPU (I don't know the details but llvmpipe driver
might be limited by single core performance so not much difference between
RPi 1 and 2) and you are forcing it to draw OpenGL which this CPU would
like to not handle at all as it is not designed for this. Already shown
example of Qt Cinematic Experience which is much more sofisticated/fancy
than your example app and can run on decent frame rates on RPi 1. Like said
earlier - do this in widgets or whatever you like technology and compare
development time (so EFL is out...) and performance (so HTML5 is out...).
Oh, and you are wrong already in a second sentence of your blog post as one
can think that there is no difference between HTML/JS app and QtQuick app.
There is. I've run Servo browser engine benchmark limited to 60 items on
i.MX6 in chromium and got 8fps. Then redo this in QtQuick and got stable
60fps. That's 7.5x better. But this discussion makes me think that I need
to do this in widgets too. Any suggestions how?

Please do not mislead people. QML is a horrible wretched thing which should
never have seen the light of day.

If there is no need for it in your specific market - it is ok. In one of a
companies I worked we had huuuge desktop application done in Qt and I will
never suggest doing it in QtQuick as widgets are perfect choice for it. But
there are many solutions where there is need for technology like
QML/QtQuick, even if it is not perfect (and it is not).

Ok, so maybe you are not misleading people with your blog post - you're
just showing them that application that is not supposed to be done with
QtQuick which requires decent HW accelerated OpenGL since December 2012
(ok, it has changed recently but still hw accelerated graphics is what you
want) when done in QtQuick and ran on weak CPU and no HW OpenGL then
performs poorly. Wow. Thanks Captain Obvious! You could have asked me and I
will tell you the result without doing anything. But guess what - it has
nothing to do with JS engine in this particular example, so your statements
are wrong.

Offering up "The Microsoft Solution" of "throw hardware and grid power at
it" is simply no solution for the vast majority of embedded systems
especially in the medical field.

On 10/19/2017 02:04 PM, Filip Piechocki wrote:

On Thu, Oct 19, 2017 at 2:43 PM, Roland Hughes <rol...@logikalsolutions.com>
wrote:

> Scroll down and watch the video. QML is an 800 lb gorilla trying to ride
> in a 2 cylinder car.
>
> http://www.logikalsolutions.com/wordpress/information-techno
> logy/raspberry-qt-part-12-qml-blows-big-stinky-chunks/
>

Application used here is of course the best candidate for widgets
implementation as it does not use QtQuick advantages.

Do this:
https://www.youtube.com/watch?v=wulbR2R1GpM
in Qt Widgets and share your results.

But please, do not mislead people. You run this app with software OpenGL on
a device with really weak CPU. Xorg alone eats all resources of RPi 1 as it
has no HW GPU acceleration.
In my company we get 20-25 fps when rendering maps on a quite powerful (for
embedded world) x86 and like 230% CPU usage (of 4 cores) as there is no
linux driver for its GPU. Meanwhile - we get stable 60fps on i.MX6 DualLite
(2 ARMv7 cores 792MHz) with 12-20% CPU usage. All done with QtQuick.


> Nasty worthless resource pig which exists only to pursue script kiddies.
>
> On 10/19/2017 04:38 AM, Vlad Stelmahovsky wrote:
>
> QML is not that resource hogging as JS. dont use JS and you'll be fine
>
> On Tue, Oct 17, 2017 at 8:11 PM, Roland Hughes <
> rol...@logikalsolutions.com> wrote:
>
>>
>>
>> On 10/17/2017 12:54 PM, interest-requ...@qt-project.org wrote:
>>
>> On ter?a-feira, 17 de outubro de 2017 08:11:13 PDT Roland Hughes wrote:
>>
>> The bug tracking system is under our control - it will not just
>> di

Re: [Interest] Interest Digest Wiki instructions for PI cross compile do not work for PostgreSQL support

[Filip Piechocki]

On Thu, Oct 19, 2017 at 2:43 PM, Roland Hughes 
wrote:

> Scroll down and watch the video. QML is an 800 lb gorilla trying to ride
> in a 2 cylinder car.
>
> http://www.logikalsolutions.com/wordpress/information-
> technology/raspberry-qt-part-12-qml-blows-big-stinky-chunks/
>

Application used here is of course the best candidate for widgets
implementation as it does not use QtQuick advantages.

Do this:
https://www.youtube.com/watch?v=wulbR2R1GpM
in Qt Widgets and share your results.

But please, do not mislead people. You run this app with software OpenGL on
a device with really weak CPU. Xorg alone eats all resources of RPi 1 as it
has no HW GPU acceleration.
In my company we get 20-25 fps when rendering maps on a quite powerful (for
embedded world) x86 and like 230% CPU usage (of 4 cores) as there is no
linux driver for its GPU. Meanwhile - we get stable 60fps on i.MX6 DualLite
(2 ARMv7 cores 792MHz) with 12-20% CPU usage. All done with QtQuick.


> Nasty worthless resource pig which exists only to pursue script kiddies.
>
> On 10/19/2017 04:38 AM, Vlad Stelmahovsky wrote:
>
> QML is not that resource hogging as JS. dont use JS and you'll be fine
>
> On Tue, Oct 17, 2017 at 8:11 PM, Roland Hughes <
> rol...@logikalsolutions.com> wrote:
>
>>
>>
>> On 10/17/2017 12:54 PM, interest-requ...@qt-project.org wrote:
>>
>> On ter?a-feira, 17 de outubro de 2017 08:11:13 PDT Roland Hughes wrote:
>>
>> The bug tracking system is under our control - it will not just
>> disappear (from our perspective).
>>
>> Oh yes it will!
>>
>> Speaking as someone who has heard that soo many times before, let's
>> just count a few for Qt shall we.
>>
>> The Trolltech bug database was never going to just disappear (from our
>> perspective). It did. A tiny fraction of the bugs migrated to the new
>> system but most were mass exterminated with
>>
>> The TT TT was not a public database. It existed internally only. When we
>> switched to a public bugtracker, we could only export some entries since many
>> had confidential customer information. Those that were exported had to be
>> review by a person to make sure we were not violation any NDAs or
>> confidentiality.
>>
>> That's the same reason why the code repository starts with Qt 4.5, not 
>> earlier
>> versions.
>>
>>
>> "The version this bug is reported against is no longer supported..."
>>
>> The Nokia bug tracker was never going to just disappear (from our
>> perspective). It did. Few, if any of the older bugs made it into the
>> current database. Most were mass exterminated with
>>
>> There was no Nokia database. We switched straight from the internal tdb
>> (that's what it was called) to JIRA.
>>
>> There was a Nokia bug base as well, at least for a while. I and others
>> entered bugs into it back in the day. Your argument also re-enforces a
>> great many bugs "simply disappeared."
>>
>> I hear from quite a few companies in similar boats. They started
>> development for a medical/industrial device which had a lengthy
>> testing/approval process, filed bug reports for that version only to see
>> them rot or fall victim to a mass extermination.
>>
>> Most open source projects don't support old versions, since they don't have
>> the manpower to do so.
>>
>>
>> The current owners of Qt and the current OpenSource maintainers don't
>> offer or seem to understand the concept of an LTS (Long Term Support)
>> version. They are constantly pursuing script kiddies and that worthless
>> QML instead of maintaining the base which built them. This will soon
>> force a fork in the OpenSource project. One which rips out all of the
>> QML and focuses on nothing but bug fixes for 12 years. Yes, 12 years.
>>
>> Again, offence taken.
>>
>> Take all of the offense you want. Medical devices and industrial controls
>> need LTS versions, not resource hogging QML features. Qt's chasing of the
>> idiot phone market which has 6 months at best life spans is alienating and
>> chasing away the very industries which made Qt successful.
>>
>> I don't know who plans on forking. There's no such division in the community,
>> so any attempt to do so will probably start with very few developers. Almost
>> certainly, fewer than critical mass to maintain the codebase.
>>
>> See TQt (Trinity Project) for an example of a fork attempt.
>>
>> It's easy to fork something you have been maintaining internally for
>> years. There _IS_ such a division. You don't know about it because they
>> don't come here. They justifiably believe they've been abandoned. The
>> relentless pursuit of "new cool features" to please the phone crowd is
>> causing the much larger medical device and industrial control industries to
>> create their own LTS.
>>
>> How many questions have you seen on here over the past 18 months about Qt
>> 3? That project Harmman (sp?) calls about periodically sells north of a
>> million units per year and the company is maintaining Qt 3 on its own so
>> they can make minor product 

[Interest] QtMqtt

[Filip Piechocki]

Hi,
It's been over a month since the QtMqtt blog post (
http://blog.qt.io/blog/2017/08/14/introducing-qtmqtt-protocol/) but I can't
find the code to download. Is it already available somewhere?

Best regards,
Filip Piechocki
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] QtWebEngine on i.MX6 eglfs

[Filip Piechocki]

On Mon, Aug 14, 2017 at 3:59 PM, Michal Klocek <michal.klo...@qt.io> wrote:

> Hi
>
> The problem is that your qtwebenigne build is not detected as embedded
> build, which means it is not configured for cross compilation. You have
> couple of options to fix it:
>
> 1) in configure line use instead of platform -xplatform
> 2) or better use -sysroot, -device and device -option (see
> mkspecs/devices/ for supported list of devices)
>
> ./configure -prefix  -release  -device linux-imx6-g++
> -device-option CROSS_COMPILE=
> -sysroot 
>

But, as said, I am compiling on the i.MX6 device so I am _not_ cross
compiling as I would like to be able to compile our software (which uses
Qt) on the device in docker image.
I would be really happy to be able to cross compile Qt as the compilation
time would not take dozen hours - but then the tools (qmake etc) are
compiled only for the host system while I need them on the target system as
well - maybe there is such an option to have them there, is it?


>
> 3) configure build explicitly with embedded feature
> -feature-embedded
>

So I wold probably go with this approach.


>
> Br
>
> Michal
>
> On 08/14/2017 03:31 PM, Filip Piechocki wrote:
> > 2 -platform
>
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] QtWebEngine on i.MX6 eglfs

[Filip Piechocki]

I am compiling Qt 5.9.1 inside a docker container running on the i.MX6
itself. My configure line:

./configure -opengl es2 -platform linux-imx6-g++ -prefix /usr -opensource
-confirm-license -release -c++std c++1z -make libs -nomake tests \
-skip qtdatavis3d \
-skip qt3d \
-skip qtconnectivity \
-skip qtgamepad \
-skip qtcharts \
-skip qtpurchasing \
-skip qtscript

I;ve created a platform mkspec to get the i.MX6 specific device settings:

$ cat qmake.conf
#
# qmake configuration for linux-g++
#
QT_QPA_DEFAULT_PLATFORM = eglfs
MAKEFILE_GENERATOR  = UNIX
CONFIG += incremental
QMAKE_INCREMENTAL_STYLE = sublib

include(../common/linux.conf)
include(../common/gcc-base-unix.conf)
include(../common/g++-unix.conf)

QMAKE_LIBS_EGL += -lEGL -lGAL
QMAKE_LIBS_OPENGL_ES2  += -lGLESv2 -lEGL -lGAL
QMAKE_LIBS_OPENVG  += -lOpenVG -lEGL -lGAL

IMX6_CFLAGS = -march=armv7-a -mfpu=neon -DLINUX=1 -DEGL_API_FB=1
QMAKE_CFLAGS   += $$IMX6_CFLAGS
QMAKE_CXXFLAGS += $$IMX6_CFLAGS

COMPILER_FLAGS += -mfloat-abi=hard
LINKER_FLAGS   += -mfloat-abi=hard

EGLFS_DEVICE_INTEGRATION = eglfs_viv

load(qt_config)

There were some QtWebEngine deps lacking (libdbus-1-dev, gperf, bison,
flex) when compiling Qt, so then I did:

$ cd qtwebengine
$ qmake
$ make


On Mon, Aug 14, 2017 at 2:42 PM, Michal Klocek <michal.klo...@qt.io> wrote:

> Hi
>
> Which version of qt is it ?
>
> Can you paste your configure line ?
>
> Br
>
> Michal
>
> On 08/14/2017 12:47 PM, Filip Piechocki wrote:
> > Hi,
> > I would like to build QtWebEngine for my i.MX6 DualLite but I am using
> > eglfs only (no X11) while I got those errors while compiling QtWebEngine:
> >
> > [1/16161] CXX obj/third_party/angle/angle_common/utilities.o
> > FAILED: obj/third_party/angle/angle_common/utilities.o
> > /usr/bin/g++ -MMD -MF obj/third_party/angle/angle_common/utilities.o.d
> > -DV8_DEPRECATION_WARNINGS -DENABLE_PLUGINS=1 -DENABLE_PDF=1 -DUSE_UDEV
> > -DUSE_AURA=1 -DUSE_GLIB=1 -DUSE_OPENSSL_CERTS=1 -DUSE_X11=1
> > -DNO_TCMALLOC -DENABLE_WEBRTC=1 -DDISABLE_NACL -DENABLE_TASK_MANAGER=1
> > -DENABLE_THEMES=1 -DFULL_SAFE_BROWSING -DSAFE_BROWSING_CSD
> > -DSAFE_BROWSING_DB_LOCAL -DCHROMIUM_BUILD -DFIELDTRIAL_TESTING_ENABLED
> > -DTOOLKIT_QT -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE
> > -D_LARGEFILE64_SOURCE -D__STDC_CONSTANT_MACROS -D__STDC_FORMAT_MACROS
> > -DNDEBUG -DNVALGRIND -DDYNAMIC_ANNOTATIONS_ENABLED=0
> > -I../../3rdparty/chromium/third_party/angle/src/common/
> third_party/numerics
> > -I../../3rdparty/chromium/third_party/angle/include
> > -I../../3rdparty/chromium/third_party/angle/src -Igen/angle
> > -fno-strict-aliasing --param=ssp-buffer-size=4 -fstack-protector
> > -funwind-tables -fPIC -pipe -pthread -march=armv7-a -mfloat-abi=hard
> > -mtune=generic-armv7-a -mfpu=neon -mthumb -Wall -U_FORTIFY_SOURCE
> > -D_FORTIFY_SOURCE=2 -Wno-psabi -Wno-unused-local-typedefs
> > -Wno-maybe-uninitialized -Wno-missing-field-initializers
> > -Wno-unused-parameter -O2 -fno-ident -fdata-sections -ffunction-sections
> > -g0 -fvisibility=hidden -fno-threadsafe-statics
> > -fvisibility-inlines-hidden -std=gnu++11 -fno-delete-null-pointer-checks
> > -Wno-narrowing -fno-rtti -fno-exceptions -c
> > ../../3rdparty/chromium/third_party/angle/src/common/utilities.cpp -o
> > obj/third_party/angle/angle_common/utilities.o
> > In file included from
> > ../../3rdparty/chromium/third_party/angle/include/EGL/egl.h:39:0,
> >  from
> > ../../3rdparty/chromium/third_party/angle/src/common/utilities.h:12,
> >  from
> > ../../3rdparty/chromium/third_party/angle/src/common/utilities.cpp:9:
> > ../../3rdparty/chromium/third_party/angle/include/EGL/
> eglplatform.h:111:22:
> > fatal error: X11/Xlib.h: No such file or directory
> >  #include 
> >   ^
> > compilation terminated.
> >
> > I see there -DUSE_X11=1 but I don't want it. Is it somehow autodetected?
> > There are some X11 libs in the system as they were installed as some
> > gstreamer plugins dependencies but the whole Qt is configured with eglfs
> > i.MX6 platform plugin with -DLINUX=1 and -DEGL_API_FB=1
> >
> > Best regards,
> > Filip Piechocki
> >
> >
> > ___
> > Interest mailing list
> > Interest@qt-project.org
> > http://lists.qt-project.org/mailman/listinfo/interest
> >
>
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

[Interest] QtWebEngine on i.MX6 eglfs

[Filip Piechocki]

Hi,
I would like to build QtWebEngine for my i.MX6 DualLite but I am using
eglfs only (no X11) while I got those errors while compiling QtWebEngine:

[1/16161] CXX obj/third_party/angle/angle_common/utilities.o
FAILED: obj/third_party/angle/angle_common/utilities.o
/usr/bin/g++ -MMD -MF obj/third_party/angle/angle_common/utilities.o.d
-DV8_DEPRECATION_WARNINGS -DENABLE_PLUGINS=1 -DENABLE_PDF=1 -DUSE_UDEV
-DUSE_AURA=1 -DUSE_GLIB=1 -DUSE_OPENSSL_CERTS=1 -DUSE_X11=1 -DNO_TCMALLOC
-DENABLE_WEBRTC=1 -DDISABLE_NACL -DENABLE_TASK_MANAGER=1 -DENABLE_THEMES=1
-DFULL_SAFE_BROWSING -DSAFE_BROWSING_CSD -DSAFE_BROWSING_DB_LOCAL
-DCHROMIUM_BUILD -DFIELDTRIAL_TESTING_ENABLED -DTOOLKIT_QT
-D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE
-D__STDC_CONSTANT_MACROS -D__STDC_FORMAT_MACROS -DNDEBUG -DNVALGRIND
-DDYNAMIC_ANNOTATIONS_ENABLED=0
-I../../3rdparty/chromium/third_party/angle/src/common/third_party/numerics
-I../../3rdparty/chromium/third_party/angle/include
-I../../3rdparty/chromium/third_party/angle/src -Igen/angle
-fno-strict-aliasing --param=ssp-buffer-size=4 -fstack-protector
-funwind-tables -fPIC -pipe -pthread -march=armv7-a -mfloat-abi=hard
-mtune=generic-armv7-a -mfpu=neon -mthumb -Wall -U_FORTIFY_SOURCE
-D_FORTIFY_SOURCE=2 -Wno-psabi -Wno-unused-local-typedefs
-Wno-maybe-uninitialized -Wno-missing-field-initializers
-Wno-unused-parameter -O2 -fno-ident -fdata-sections -ffunction-sections
-g0 -fvisibility=hidden -fno-threadsafe-statics -fvisibility-inlines-hidden
-std=gnu++11 -fno-delete-null-pointer-checks -Wno-narrowing -fno-rtti
-fno-exceptions -c
../../3rdparty/chromium/third_party/angle/src/common/utilities.cpp -o
obj/third_party/angle/angle_common/utilities.o
In file included from
../../3rdparty/chromium/third_party/angle/include/EGL/egl.h:39:0,
 from
../../3rdparty/chromium/third_party/angle/src/common/utilities.h:12,
 from
../../3rdparty/chromium/third_party/angle/src/common/utilities.cpp:9:
../../3rdparty/chromium/third_party/angle/include/EGL/eglplatform.h:111:22:
fatal error: X11/Xlib.h: No such file or directory
 #include 
  ^
compilation terminated.

I see there -DUSE_X11=1 but I don't want it. Is it somehow autodetected?
There are some X11 libs in the system as they were installed as some
gstreamer plugins dependencies but the whole Qt is configured with eglfs
i.MX6 platform plugin with -DLINUX=1 and -DEGL_API_FB=1

Best regards,
Filip Piechocki
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

[Interest] Dual screen Wayland on i.MX6

[Filip Piechocki]

Hi,

I would like to run our Qt application (it is basically displaying several
QWebEngineViews) in a dual screen setup on the i.MX6 board. Those screens
are connected to LVDS - one is on /dev/fb0 and the second is on /dev/fb2.
We are able to achieve what we want by running Xorg with 2 devices and 2
screens in configuration. The device Xorg driver has to be "fbdev" as
"vivante" xorg driver works only with /dev/fb0 (checked - while X starts
fine it crashes when trying to run OpenGL application on the second
screen). So we do not have hardware accelerated OpenGL which is a huge
performance hit.

So my question is:
Is it possible to run some simple QtWayland compositor that would control
both displays? So we can have one HW accelerated application displayed on
both screens? Or maybe some other way to get this working? And how should I
setup the Vivante libraries to make the QtWayland compositor and other
applications to run (I mean there are libEGL-fb.so and libEGL-wl.so while
the compositor should be ran with eglfs and other apps with wayland
platform plugin, right?)

Best Regards,
Filip Piechocki
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] Quick2 OpenGL inefficiency?

[Filip Piechocki]

I don't know how you produce the video frames, but check that the software
you are using might be able to produce OpenGL texture directly (not the
buffer data). If not then here are some useful links:
http://stackoverflow.com/questions/9863969/updating-a-texture-in-opengl-with-glteximage2d
http://www.gamedev.net/topic/641283-fastest-way-to-stream-video-to-texture/

So basically you'll need to use glTexSubImage2D directly (and you probably
do not need QImage at all) and for custom OpenGL rendering you can use
QQuickFramebufferObject as your DisplayItem:
http://blog.qt.io/blog/2015/05/11/integrating-custom-opengl-rendering-with-qt-quick-via-qquickframebufferobject/

On Tue, Mar 8, 2016 at 7:00 AM, Jani Tykka <jty...@broadsoft.com> wrote:

> I'm creating the image from buffer which is unsigned char buffer
> containing video frame data
> QImage( buffer, width, height, QImage::Format_RGB32 );
>
>
>
> On Mon, Mar 7, 2016 at 10:05 PM, Filip Piechocki <fpiecho...@gmail.com>
> wrote:
> >
> > How are you generating those images? What do they represent?
> >
> > On Mar 7, 2016 20:55, "Jani Tykka" <jty...@broadsoft.com> wrote:
> >>
> >> Images are passed from another thread in rate 15-30 fps. Is there an
> example available how to achieve Image to OpenGL texture and use it in
> scene graph?
> >>
> >> On Mon, Mar 7, 2016 at 5:11 PM, Filip Piechocki <fpiecho...@gmail.com>
> wrote:
> >>>
> >>> And where it comes from? How frequent it happens? Probably the best
> thing here would be to generate this image as an OpenGL texture and then
> use in the Qt's scene graph.
> >>>
> >>> On Mon, Mar 7, 2016 at 4:04 PM, Jani Tykka <jty...@broadsoft.com>
> wrote:
> >>>>
> >>>> Yes, the image is always changed when the update is invoked.
> >>>>
> >>>> On Mon, Mar 7, 2016 at 4:43 PM, Filip Piechocki <fpiecho...@gmail.com>
> wrote:
> >>>>>
> >>>>> Hi,
> >>>>>
> >>>>> Why are you re-creating the texture on every node update? Does the
> m_Renderer->getImage() really changes? My first guess would be that the
> texture creation from image is the most costly part here (uploading the
> texture to GPU?) and I would do this only if necessary (the image really
> changes).
> >>>>>
> >>>>> BR,
> >>>>> Filip
> >>>>>
> >>>>> On Mon, Mar 7, 2016 at 3:04 PM, Jani Tykka <jty...@broadsoft.com>
> wrote:
> >>>>>>
> >>>>>> Hi,
> >>>>>>
> >>>>>> We are rendering QImages on QQuickItem as following:
> >>>>>>
> >>>>>> QSGNode * DisplayItem::updatePaintNode( QSGNode * node,
> UpdatePaintNodeData * /*data*/ )
> >>>>>>
> >>>>>> {
> >>>>>>
> >>>>>> QSGSimpleTextureNode * n = static_cast< QSGSimpleTextureNode* >(
> node );
> >>>>>>
> >>>>>> if ( !n )
> >>>>>>
> >>>>>> n = new QSGSimpleTextureNode;
> >>>>>>
> >>>>>>
> >>>>>> n->setRect( 0, 0, width(), height() );
> >>>>>>
> >>>>>>
> >>>>>> delete m_Texture;
> >>>>>>
> >>>>>>
> >>>>>> m_Texture = window()->createTextureFromImage(
> m_Renderer->getImage() );
> >>>>>>
> >>>>>> n->setTexture( m_Texture );
> >>>>>>
> >>>>>>
> >>>>>> return n;
> >>>>>>
> >>>>>> }
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>> It seems that computers with separate GPU there is a decent amount
> of CPU utilised. We are running into problems if the machine lacks GPU,
> then with large images the CPU usage grows drastically. Any suggestions how
> to improve large image painting on QQuickItem? With Quick1 and painting
> directly on HWND/CocoaWindow we didn't experience this high CPU usage.
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>> This email is intended solely for the person or entity to which it
> is addressed and may contain confidential and/or privileged information. If
> you are not the intended recipient and have received this email in error,
> please notify BroadSoft, Inc. immediatel

Re: [Interest] Quick2 OpenGL inefficiency?

[Filip Piechocki]

How are you generating those images? What do they represent?
On Mar 7, 2016 20:55, "Jani Tykka" <jty...@broadsoft.com> wrote:

> Images are passed from another thread in rate 15-30 fps. Is there an
> example available how to achieve Image to OpenGL texture and use it in
> scene graph?
>
> On Mon, Mar 7, 2016 at 5:11 PM, Filip Piechocki <fpiecho...@gmail.com>
> wrote:
>
>> And where it comes from? How frequent it happens? Probably the best thing
>> here would be to generate this image as an OpenGL texture and then use in
>> the Qt's scene graph.
>>
>> On Mon, Mar 7, 2016 at 4:04 PM, Jani Tykka <jty...@broadsoft.com> wrote:
>>
>>> Yes, the image is always changed when the update is invoked.
>>>
>>> On Mon, Mar 7, 2016 at 4:43 PM, Filip Piechocki <fpiecho...@gmail.com>
>>> wrote:
>>>
>>>> Hi,
>>>>
>>>> Why are you re-creating the texture on every node update? Does the
>>>> m_Renderer->getImage() really changes? My first guess would be that the
>>>> texture creation from image is the most costly part here (uploading the
>>>> texture to GPU?) and I would do this only if necessary (the image really
>>>> changes).
>>>>
>>>> BR,
>>>> Filip
>>>>
>>>> On Mon, Mar 7, 2016 at 3:04 PM, Jani Tykka <jty...@broadsoft.com>
>>>> wrote:
>>>>
>>>>> Hi,
>>>>>
>>>>> We are rendering QImages on QQuickItem as following:
>>>>>
>>>>> QSGNode * DisplayItem::updatePaintNode( QSGNode * node, 
>>>>> UpdatePaintNodeData * /*data*/ )
>>>>>
>>>>> {
>>>>>
>>>>>   QSGSimpleTextureNode * n = static_cast< QSGSimpleTextureNode* >( node );
>>>>>
>>>>>   if ( !n )
>>>>>
>>>>>   n = new QSGSimpleTextureNode;
>>>>>
>>>>>
>>>>>   n->setRect( 0, 0, width(), height() );
>>>>>
>>>>>
>>>>>   delete m_Texture;
>>>>>
>>>>>
>>>>>   m_Texture = window()->createTextureFromImage( m_Renderer->getImage() );
>>>>>
>>>>>   n->setTexture( m_Texture );
>>>>>
>>>>>
>>>>>   return n;
>>>>>
>>>>> }
>>>>>
>>>>>
>>>>>
>>>>> It seems that computers with separate GPU there is a decent amount of CPU 
>>>>> utilised. We are running into problems if the machine lacks GPU, then 
>>>>> with large images the CPU usage grows drastically. Any suggestions how to 
>>>>> improve large image painting on QQuickItem? With Quick1 and painting 
>>>>> directly on HWND/CocoaWindow we didn't experience this high CPU usage.
>>>>>
>>>>>
>>>>>
>>>>> This email is intended solely for the person or entity to which it is
>>>>> addressed and may contain confidential and/or privileged information. If
>>>>> you are not the intended recipient and have received this email in error,
>>>>> please notify BroadSoft, Inc. immediately by replying to this message, and
>>>>> destroy all copies of this message, along with any attachment, prior to
>>>>> reading, distributing or copying it.
>>>>>
>>>>> ___
>>>>> Interest mailing list
>>>>> Interest@qt-project.org
>>>>> http://lists.qt-project.org/mailman/listinfo/interest
>>>>>
>>>>>
>>>>
>>>
>>>
>>> --
>>> *Jani Tykkä*
>>> Development Manager | BroadSoft, Inc. | +358 44 596 0587 |
>>> jty...@broadsoft.com
>>>
>>>
>>> This email is intended solely for the person or entity to which it is
>>> addressed and may contain confidential and/or privileged information. If
>>> you are not the intended recipient and have received this email in error,
>>> please notify BroadSoft, Inc. immediately by replying to this message, and
>>> destroy all copies of this message, along with any attachment, prior to
>>> reading, distributing or copying it.
>>>
>>
>>
>
>
> --
> *Jani Tykkä*
> Development Manager | BroadSoft, Inc. | +358 44 596 0587 |
> jty...@broadsoft.com
>
>
> This email is intended solely for the person or entity to which it is
> addressed and may contain confidential and/or privileged information. If
> you are not the intended recipient and have received this email in error,
> please notify BroadSoft, Inc. immediately by replying to this message, and
> destroy all copies of this message, along with any attachment, prior to
> reading, distributing or copying it.
>
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] Quick2 OpenGL inefficiency?

[Filip Piechocki]

And where it comes from? How frequent it happens? Probably the best thing
here would be to generate this image as an OpenGL texture and then use in
the Qt's scene graph.

On Mon, Mar 7, 2016 at 4:04 PM, Jani Tykka <jty...@broadsoft.com> wrote:

> Yes, the image is always changed when the update is invoked.
>
> On Mon, Mar 7, 2016 at 4:43 PM, Filip Piechocki <fpiecho...@gmail.com>
> wrote:
>
>> Hi,
>>
>> Why are you re-creating the texture on every node update? Does the
>> m_Renderer->getImage() really changes? My first guess would be that the
>> texture creation from image is the most costly part here (uploading the
>> texture to GPU?) and I would do this only if necessary (the image really
>> changes).
>>
>> BR,
>> Filip
>>
>> On Mon, Mar 7, 2016 at 3:04 PM, Jani Tykka <jty...@broadsoft.com> wrote:
>>
>>> Hi,
>>>
>>> We are rendering QImages on QQuickItem as following:
>>>
>>> QSGNode * DisplayItem::updatePaintNode( QSGNode * node, UpdatePaintNodeData 
>>> * /*data*/ )
>>>
>>> {
>>>
>>> QSGSimpleTextureNode * n = static_cast< QSGSimpleTextureNode* >( node );
>>>
>>> if ( !n )
>>>
>>> n = new QSGSimpleTextureNode;
>>>
>>>
>>> n->setRect( 0, 0, width(), height() );
>>>
>>>
>>> delete m_Texture;
>>>
>>>
>>> m_Texture = window()->createTextureFromImage( m_Renderer->getImage() );
>>>
>>> n->setTexture( m_Texture );
>>>
>>>
>>> return n;
>>>
>>> }
>>>
>>>
>>>
>>> It seems that computers with separate GPU there is a decent amount of CPU 
>>> utilised. We are running into problems if the machine lacks GPU, then with 
>>> large images the CPU usage grows drastically. Any suggestions how to 
>>> improve large image painting on QQuickItem? With Quick1 and painting 
>>> directly on HWND/CocoaWindow we didn't experience this high CPU usage.
>>>
>>>
>>>
>>> This email is intended solely for the person or entity to which it is
>>> addressed and may contain confidential and/or privileged information. If
>>> you are not the intended recipient and have received this email in error,
>>> please notify BroadSoft, Inc. immediately by replying to this message, and
>>> destroy all copies of this message, along with any attachment, prior to
>>> reading, distributing or copying it.
>>>
>>> ___
>>> Interest mailing list
>>> Interest@qt-project.org
>>> http://lists.qt-project.org/mailman/listinfo/interest
>>>
>>>
>>
>
>
> --
> *Jani Tykkä*
> Development Manager | BroadSoft, Inc. | +358 44 596 0587 |
> jty...@broadsoft.com
>
>
> This email is intended solely for the person or entity to which it is
> addressed and may contain confidential and/or privileged information. If
> you are not the intended recipient and have received this email in error,
> please notify BroadSoft, Inc. immediately by replying to this message, and
> destroy all copies of this message, along with any attachment, prior to
> reading, distributing or copying it.
>
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] Quick2 OpenGL inefficiency?

[Filip Piechocki]

Hi,

Why are you re-creating the texture on every node update? Does the
m_Renderer->getImage() really changes? My first guess would be that the
texture creation from image is the most costly part here (uploading the
texture to GPU?) and I would do this only if necessary (the image really
changes).

BR,
Filip

On Mon, Mar 7, 2016 at 3:04 PM, Jani Tykka  wrote:

> Hi,
>
> We are rendering QImages on QQuickItem as following:
>
> QSGNode * DisplayItem::updatePaintNode( QSGNode * node, UpdatePaintNodeData * 
> /*data*/ )
>
> {
>
>   QSGSimpleTextureNode * n = static_cast< QSGSimpleTextureNode* >( node );
>
>   if ( !n )
>
>   n = new QSGSimpleTextureNode;
>
>
>   n->setRect( 0, 0, width(), height() );
>
>
>   delete m_Texture;
>
>
>   m_Texture = window()->createTextureFromImage( m_Renderer->getImage() );
>
>   n->setTexture( m_Texture );
>
>
>   return n;
>
> }
>
>
>
> It seems that computers with separate GPU there is a decent amount of CPU 
> utilised. We are running into problems if the machine lacks GPU, then with 
> large images the CPU usage grows drastically. Any suggestions how to improve 
> large image painting on QQuickItem? With Quick1 and painting directly on 
> HWND/CocoaWindow we didn't experience this high CPU usage.
>
>
>
> This email is intended solely for the person or entity to which it is
> addressed and may contain confidential and/or privileged information. If
> you are not the intended recipient and have received this email in error,
> please notify BroadSoft, Inc. immediately by replying to this message, and
> destroy all copies of this message, along with any attachment, prior to
> reading, distributing or copying it.
>
> ___
> Interest mailing list
> Interest@qt-project.org
> http://lists.qt-project.org/mailman/listinfo/interest
>
>
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] QML element from QWidget based class

[Filip Piechocki]

You mean QML or QtQuick? If you want to instantiate widgets from QML then I
think this should not be a problem (as you can instatiate there any
QObject), just expose them to QML engine. If you mean embedding QWidget in
a QtQuick application, then Olivier gave you the answer.

BR,
Filip

On Wed, Nov 26, 2014 at 6:28 AM, Igor Mironchik igor.mironc...@gmail.com
wrote:

   Hi guys,

 Is it possible to use QWidget based components in QML?

 What this QWidget based class have to do for it?

 Thanks.

 ___
 Interest mailing list
 Interest@qt-project.org
 http://lists.qt-project.org/mailman/listinfo/interest


___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] Regarding auto resizing of the QtQuick window for embedded device

[Filip Piechocki]

With eglfs you're application would always be resized to fullscreen. So
your window DOES NOT have 2000x800 - it has 1920x1080. You can check your
current fb mode (on Ubuntu on wandboard it is
in: /sys/devices/platform/mxc_sdc_fb.0/graphics/fb0/modes) and available
modes (wandboard: /sys/devices/platform/mxc_sdc_fb.0/graphics/fb0/modes).
And with eglfs your window would always be covering whole framebuffer. So
if you want your content be in a different size, the you have create some
root element, like black rectangle, which is going to fill the screen and
then the jest of your app is positioned in this rectangle. So if you have
such application:

Window {
  width: 320
  height: 200
  Image {
anchors.fill: parent
source: some/source
  }
}

And you want it to still be 320x200 on your hd monitor with eglfs, then you
can do:

Window {
  Rectangle {
width: 320
height: 200
color: black
Image {
  anchors.fill: parent
  source: some/source
}
  }
}

So this rectangle becomes the background filling the rest of the screen.
But I am really wondering how you are going to display somethig 2000 pixels
wide on the monitor which is only 1920 pixels wide.

BR,
Filip

On Thu, Nov 6, 2014 at 9:55 AM, Jha Sonakumar sona@techmahindra.com
wrote:

   Hi,


  Let me explain my problem clearly. 2000x800 has come from the below
 existing code in my application main.qml.


  Window {
 id: root
 visible: true
 width: 2000
 height: 800


 SplitView {
 anchors.fill: parent
 orientation: Qt.Horizontal

 Item {
 id: driveInfo
 width: 1000
 height: 800


 Layout.minimumWidth: 640
 Layout.fillWidth: true
 Layout.minimumHeight: 480
 Layout.fillHeight: true

   ...

 }


 Item {
 id: ivi

 width: 1000
 height: 800

 Layout.fillWidth: true

 Layout.fillHeight: true
...
...
 }
}
 }


  I would like to see 2000*480 to fit both displays by modifying the top
 width and height. However, it scales to full screen. am testing on HD
 monitor display having resolution 1920X1080.


  Inorder to achieve 1000*480 on each of split view displays, Do I need to
 set any environment variable on embedded linux with eglfs as QPA plugin?


  I tried to set using environment variables mentioned in
 http://qt-project.org/doc/qt-5/embedded-linux.html with no success.


  Please let me know if there is any solution for the same in this regard.


  Thanks and Regards,

 Sona


  --
 *From:* Filip Piechocki fpiecho...@gmail.com
 *Sent:* Wednesday, November 5, 2014 6:11 PM

 *To:* Jha Sonakumar
 *Cc:* interest@qt-project.org Interest
 *Subject:* Re: [Interest] Regarding auto resizing of the QtQuick window
 for embedded device

  I give up :) If you've found that you can set some environment variables
 and they are described on this page - what more can I tell? Just read this
 page. And I don't know what width and height you've set. And I don't know
 where those 2000x800 come from. To be honest - now I am not sure what the
 problem is. How can I help you then?

 On Wed, Nov 5, 2014 at 1:35 PM, Jha Sonakumar sona@techmahindra.com
 wrote:

  We already set the width and height.
  --
 *From:* Filip Piechocki fpiecho...@gmail.com
 *Sent:* Wednesday, November 5, 2014 6:00 PM

 *To:* Jha Sonakumar
 *Cc:* interest@qt-project.org Interest
 *Subject:* Re: [Interest] Regarding auto resizing of the QtQuick window
 for embedded device

   How you know that currently it uses 2000x800?

 On Wed, Nov 5, 2014 at 12:09 PM, Jha Sonakumar sona@techmahindra.com
  wrote:

  Hi Filip

 My display is HD Monitor is 1920X1080,we'd like to connect twin lcd
 displays each of 1280X480. I would like ensure,whether my application
 window will fit to the display or not.

 Currently my application uses widthxheight :(2000x800)

 Is there environment-variable to be set ?


  BR

 SonaKumar


  --
 *From:* Filip Piechocki fpiecho...@gmail.com
 *Sent:* Wednesday, November 5, 2014 4:28 PM

 *To:* Jha Sonakumar
 *Cc:* interest@qt-project.org Interest
 *Subject:* Re: [Interest] Regarding auto resizing of the QtQuick window
 for embedded device

   Like I said - your Window will always be covering whole screen.
 That's how the 'eglfs' plugin works. Why do you want it to cover only a
 part of screen?

 On Wed, Nov 5, 2014 at 11:47 AM, Jha Sonakumar 
 sona@techmahindra.com wrote:

  Hi Filip

 i tried with the following code:

 Window {
 visible: true
 width: 1200
 height: 480

 Rectangle{
 id:rect
 color:black
 anchors.fill: parent

 Item

Re: [Interest] Regarding auto resizing of the QtQuick window for embedded device

[Filip Piechocki]

Hi,
What QPA plugin are you using?

BR,
Filip

On Wed, Nov 5, 2014 at 10:17 AM, Jha Sonakumar sona@techmahindra.com
wrote:

  Hi All,


  I have developed an application using QtQuick 2.0 for IMX 6 board. The
 view window has been automatically resized to cover whole display
 irrespective of specified width height.


  Display size  :(2560X800)


  But i need to show the QtQuick window of size (2560X480).



  Would you please guide me to resolve the issue.



  Best Regards

 SonaKumar

 --

 
 Disclaimer: This message and the information contained herein is
 proprietary and confidential and subject to the Tech Mahindra policy
 statement, you may review the policy at
 http://www.techmahindra.com/Disclaimer.html externally
 http://tim.techmahindra.com/tim/disclaimer.html internally within
 TechMahindra.

 


 ___
 Interest mailing list
 Interest@qt-project.org
 http://lists.qt-project.org/mailman/listinfo/interest


___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] Regarding auto resizing of the QtQuick window for embedded device

[Filip Piechocki]

On Wed, Nov 5, 2014 at 10:32 AM, Jha Sonakumar sona@techmahindra.com
wrote:

  sory.. what do u mean by QPA?

Platform Abstraction plugin. Are you using X11? If yes then you are
probably using 'xcb' QPA plugin, but I guess you are not using X11, a then
'eglfs' plugin is what you use, right?


  --
 *From:* interest-bounces+sona.jha=techmahindra@qt-project.org
 interest-bounces+sona.jha=techmahindra@qt-project.org on behalf of
 Filip Piechocki fpiecho...@gmail.com
 *Sent:* Wednesday, November 5, 2014 2:56 PM
 *To:* Jha Sonakumar
 *Cc:* interest@qt-project.org
 *Subject:* Re: [Interest] Regarding auto resizing of the QtQuick window
 for embedded device

   Hi,
 What QPA plugin are you using?

  BR,
 Filip

 On Wed, Nov 5, 2014 at 10:17 AM, Jha Sonakumar sona@techmahindra.com
 wrote:

  Hi All,


  I have developed an application using QtQuick 2.0 for IMX 6 board. The
 view window has been automatically resized to cover whole display
 irrespective of specified width height.


  Display size  :(2560X800)


  But i need to show the QtQuick window of size (2560X480).



  Would you please guide me to resolve the issue.



  Best Regards

 SonaKumar

 --

 
 Disclaimer: This message and the information contained herein is
 proprietary and confidential and subject to the Tech Mahindra policy
 statement, you may review the policy at
 http://www.techmahindra.com/Disclaimer.html externally
 http://tim.techmahindra.com/tim/disclaimer.html internally within
 TechMahindra.

 


 ___
 Interest mailing list
 Interest@qt-project.org
 http://lists.qt-project.org/mailman/listinfo/interest


   --

 
 Disclaimer: This message and the information contained herein is
 proprietary and confidential and subject to the Tech Mahindra policy
 statement, you may review the policy at
 http://www.techmahindra.com/Disclaimer.html externally
 http://tim.techmahindra.com/tim/disclaimer.html internally within
 TechMahindra.

 


___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] Regarding auto resizing of the QtQuick window for embedded device

[Filip Piechocki]

That's what I thought as with linuxfb you won't be able to use QtQuick 2.x
as it requires OpenGL.
So with 'eglfs' your application is displayed on the whole frame buffer and
so it covers whole screen. So anything you type as width and height of the
root element has no meaning as it will be resized to whole screen. I you
want it smaller then you might wrap your main element with Rectangle.
Something like this:

Window {
  Rectangle {
anchors.fill: parent
color: black

Item { // this item is representig the main item of your application
  anchors.centerIn: parent
  width: 2560
  height: 480
}
  }
}

You application will stiil be full screen, but the content will be resized
inside this black rectangle.

On Wed, Nov 5, 2014 at 10:52 AM, Jha Sonakumar sona@techmahindra.com
wrote:

  Hi Filip,


  you are right, i am using eglfs Yocto


  BR

 SonaKumar
  --
 *From:* interest-bounces+sona.jha=techmahindra@qt-project.org
 interest-bounces+sona.jha=techmahindra@qt-project.org on behalf of
 Filip Piechocki fpiecho...@gmail.com
 *Sent:* Wednesday, November 5, 2014 3:18 PM
 *To:* Jha Sonakumar; interest@qt-project.org Interest

 *Subject:* Re: [Interest] Regarding auto resizing of the QtQuick window
 for embedded device



 On Wed, Nov 5, 2014 at 10:32 AM, Jha Sonakumar sona@techmahindra.com
 wrote:

  sory.. what do u mean by QPA?

 Platform Abstraction plugin. Are you using X11? If yes then you are
 probably using 'xcb' QPA plugin, but I guess you are not using X11, a then
 'eglfs' plugin is what you use, right?


   --
 *From:* interest-bounces+sona.jha=techmahindra@qt-project.org
 interest-bounces+sona.jha=techmahindra@qt-project.org on behalf of
 Filip Piechocki fpiecho...@gmail.com
 *Sent:* Wednesday, November 5, 2014 2:56 PM
 *To:* Jha Sonakumar
 *Cc:* interest@qt-project.org
 *Subject:* Re: [Interest] Regarding auto resizing of the QtQuick window
 for embedded device

Hi,
 What QPA plugin are you using?

  BR,
 Filip

 On Wed, Nov 5, 2014 at 10:17 AM, Jha Sonakumar sona@techmahindra.com
  wrote:

  Hi All,


  I have developed an application using QtQuick 2.0 for IMX 6 board. The
 view window has been automatically resized to cover whole display
 irrespective of specified width height.


  Display size  :(2560X800)


  But i need to show the QtQuick window of size (2560X480).



  Would you please guide me to resolve the issue.



  Best Regards

 SonaKumar

 --

 
 Disclaimer: This message and the information contained herein is
 proprietary and confidential and subject to the Tech Mahindra policy
 statement, you may review the policy at
 http://www.techmahindra.com/Disclaimer.html externally
 http://tim.techmahindra.com/tim/disclaimer.html internally within
 TechMahindra.

 


 ___
 Interest mailing list
 Interest@qt-project.org
 http://lists.qt-project.org/mailman/listinfo/interest


  --

 
 Disclaimer: This message and the information contained herein is
 proprietary and confidential and subject to the Tech Mahindra policy
 statement, you may review the policy at
 http://www.techmahindra.com/Disclaimer.html externally
 http://tim.techmahindra.com/tim/disclaimer.html internally within
 TechMahindra.

 


--

 
 Disclaimer: This message and the information contained herein is
 proprietary and confidential and subject to the Tech Mahindra policy
 statement, you may review the policy at
 http://www.techmahindra.com/Disclaimer.html externally
 http://tim.techmahindra.com/tim/disclaimer.html internally within
 TechMahindra.

 


___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] Regarding auto resizing of the QtQuick window for embedded device

[Filip Piechocki]

Like I said - your Window will always be covering whole screen. That's how
the 'eglfs' plugin works. Why do you want it to cover only a part of screen?

On Wed, Nov 5, 2014 at 11:47 AM, Jha Sonakumar sona@techmahindra.com
wrote:

  Hi Filip

 i tried with the following code:

 Window {
 visible: true
 width: 1200
 height: 480

 Rectangle{
 id:rect
 color:black
 anchors.fill: parent

 Item {
 anchors.centerIn: parent
 width: 800
 height: 480
 focus:true

 Audio {
 id: player
 source:qrc:/Neela Yevaru.mp3
 autoPlay: true
 muted: false
 }

 Keys.onSpacePressed: playPauseMedia()

 function playPauseMedia(){
 switch(player.playbackState) {
 case Audio.PlayingState:
 player.pause()
 console.log(Paused media)
 break
 case Audio.PausedState:
 player.play()
 console.log(Playing media)
 break
 default:
 break
 }

 }
 }
 }
 }


  still result is same


  BR

 Sona
  --
 *From:* Filip Piechocki fpiecho...@gmail.com
 *Sent:* Wednesday, November 5, 2014 3:36 PM
 *To:* Jha Sonakumar
 *Cc:* interest@qt-project.org Interest

 *Subject:* Re: [Interest] Regarding auto resizing of the QtQuick window
 for embedded device

  That's what I thought as with linuxfb you won't be able to use QtQuick
 2.x as it requires OpenGL.
 So with 'eglfs' your application is displayed on the whole frame buffer
 and so it covers whole screen. So anything you type as width and height of
 the root element has no meaning as it will be resized to whole screen. I
 you want it smaller then you might wrap your main element with Rectangle.
 Something like this:

  Window {
   Rectangle {
 anchors.fill: parent
 color: black

  Item { // this item is representig the main item of your application
   anchors.centerIn: parent
   width: 2560
   height: 480
 }
   }
 }

  You application will stiil be full screen, but the content will be
 resized inside this black rectangle.

 On Wed, Nov 5, 2014 at 10:52 AM, Jha Sonakumar sona@techmahindra.com
 wrote:

  Hi Filip,


  you are right, i am using eglfs Yocto


  BR

 SonaKumar
  --
 *From:* interest-bounces+sona.jha=techmahindra@qt-project.org
 interest-bounces+sona.jha=techmahindra@qt-project.org on behalf of
 Filip Piechocki fpiecho...@gmail.com
 *Sent:* Wednesday, November 5, 2014 3:18 PM
 *To:* Jha Sonakumar; interest@qt-project.org Interest

 *Subject:* Re: [Interest] Regarding auto resizing of the QtQuick window
 for embedded device



 On Wed, Nov 5, 2014 at 10:32 AM, Jha Sonakumar sona@techmahindra.com
  wrote:

  sory.. what do u mean by QPA?

 Platform Abstraction plugin. Are you using X11? If yes then you are
 probably using 'xcb' QPA plugin, but I guess you are not using X11, a then
 'eglfs' plugin is what you use, right?


   --
 *From:* interest-bounces+sona.jha=techmahindra@qt-project.org
 interest-bounces+sona.jha=techmahindra@qt-project.org on behalf
 of Filip Piechocki fpiecho...@gmail.com
 *Sent:* Wednesday, November 5, 2014 2:56 PM
 *To:* Jha Sonakumar
 *Cc:* interest@qt-project.org
 *Subject:* Re: [Interest] Regarding auto resizing of the QtQuick window
 for embedded device

Hi,
 What QPA plugin are you using?

  BR,
 Filip

 On Wed, Nov 5, 2014 at 10:17 AM, Jha Sonakumar 
 sona@techmahindra.com wrote:

  Hi All,


  I have developed an application using QtQuick 2.0 for IMX 6 board.
 The view window has been automatically resized to cover whole display
 irrespective of specified width height.


  Display size  :(2560X800)


  But i need to show the QtQuick window of size (2560X480).



  Would you please guide me to resolve the issue.



  Best Regards

 SonaKumar

 --

 
 Disclaimer: This message and the information contained herein is
 proprietary and confidential and subject to the Tech Mahindra policy
 statement, you may review the policy at
 http://www.techmahindra.com/Disclaimer.html externally
 http://tim.techmahindra.com/tim/disclaimer.html internally within
 TechMahindra.

 


 ___
 Interest mailing list
 Interest@qt-project.org
 http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] Regarding auto resizing of the QtQuick window for embedded device

[Filip Piechocki]

How you know that currently it uses 2000x800?

On Wed, Nov 5, 2014 at 12:09 PM, Jha Sonakumar sona@techmahindra.com
wrote:

  Hi Filip

 My display is HD Monitor is 1920X1080,we'd like to connect twin lcd
 displays each of 1280X480. I would like ensure,whether my application
 window will fit to the display or not.

 Currently my application uses widthxheight :(2000x800)

 Is there environment-variable to be set ?


  BR

 SonaKumar


  --
 *From:* Filip Piechocki fpiecho...@gmail.com
 *Sent:* Wednesday, November 5, 2014 4:28 PM

 *To:* Jha Sonakumar
 *Cc:* interest@qt-project.org Interest
 *Subject:* Re: [Interest] Regarding auto resizing of the QtQuick window
 for embedded device

  Like I said - your Window will always be covering whole screen. That's
 how the 'eglfs' plugin works. Why do you want it to cover only a part of
 screen?

 On Wed, Nov 5, 2014 at 11:47 AM, Jha Sonakumar sona@techmahindra.com
 wrote:

  Hi Filip

 i tried with the following code:

 Window {
 visible: true
 width: 1200
 height: 480

 Rectangle{
 id:rect
 color:black
 anchors.fill: parent

 Item {
 anchors.centerIn: parent
 width: 800
 height: 480
 focus:true

 Audio {
 id: player
 source:qrc:/Neela Yevaru.mp3
 autoPlay: true
 muted: false
 }

 Keys.onSpacePressed: playPauseMedia()

 function playPauseMedia(){
 switch(player.playbackState) {
 case Audio.PlayingState:
 player.pause()
 console.log(Paused media)
 break
 case Audio.PausedState:
 player.play()
 console.log(Playing media)
 break
 default:
 break
 }

 }
 }
 }
 }


  still result is same


  BR

 Sona
  --
 *From:* Filip Piechocki fpiecho...@gmail.com
 *Sent:* Wednesday, November 5, 2014 3:36 PM
 *To:* Jha Sonakumar
 *Cc:* interest@qt-project.org Interest

 *Subject:* Re: [Interest] Regarding auto resizing of the QtQuick window
 for embedded device

   That's what I thought as with linuxfb you won't be able to use QtQuick
 2.x as it requires OpenGL.
 So with 'eglfs' your application is displayed on the whole frame buffer
 and so it covers whole screen. So anything you type as width and height of
 the root element has no meaning as it will be resized to whole screen. I
 you want it smaller then you might wrap your main element with Rectangle.
 Something like this:

  Window {
   Rectangle {
 anchors.fill: parent
 color: black

  Item { // this item is representig the main item of your application
   anchors.centerIn: parent
   width: 2560
   height: 480
 }
   }
 }

  You application will stiil be full screen, but the content will be
 resized inside this black rectangle.

 On Wed, Nov 5, 2014 at 10:52 AM, Jha Sonakumar sona@techmahindra.com
  wrote:

  Hi Filip,


  you are right, i am using eglfs Yocto


  BR

 SonaKumar
  --
 *From:* interest-bounces+sona.jha=techmahindra@qt-project.org
 interest-bounces+sona.jha=techmahindra@qt-project.org on behalf
 of Filip Piechocki fpiecho...@gmail.com
 *Sent:* Wednesday, November 5, 2014 3:18 PM
 *To:* Jha Sonakumar; interest@qt-project.org Interest

 *Subject:* Re: [Interest] Regarding auto resizing of the QtQuick window
 for embedded device



 On Wed, Nov 5, 2014 at 10:32 AM, Jha Sonakumar 
 sona@techmahindra.com wrote:

  sory.. what do u mean by QPA?

 Platform Abstraction plugin. Are you using X11? If yes then you are
 probably using 'xcb' QPA plugin, but I guess you are not using X11, a then
 'eglfs' plugin is what you use, right?


   --
 *From:* interest-bounces+sona.jha=techmahindra@qt-project.org
 interest-bounces+sona.jha=techmahindra@qt-project.org on behalf
 of Filip Piechocki fpiecho...@gmail.com
 *Sent:* Wednesday, November 5, 2014 2:56 PM
 *To:* Jha Sonakumar
 *Cc:* interest@qt-project.org
 *Subject:* Re: [Interest] Regarding auto resizing of the QtQuick
 window for embedded device

Hi,
 What QPA plugin are you using?

  BR,
 Filip

 On Wed, Nov 5, 2014 at 10:17 AM, Jha Sonakumar 
 sona@techmahindra.com wrote:

  Hi All,


  I have developed an application using QtQuick 2.0 for IMX 6 board.
 The view window has been automatically resized to cover whole display
 irrespective of specified width height.


  Display size  :(2560X800)


  But i need to show the QtQuick window of size (2560X480).



  Would you please guide me to resolve the issue.



  Best Regards

 SonaKumar

Re: [Interest] Regarding auto resizing of the QtQuick window for embedded device

[Filip Piechocki]

I give up :) If you've found that you can set some environment variables
and they are described on this page - what more can I tell? Just read this
page. And I don't know what width and height you've set. And I don't know
where those 2000x800 come from. To be honest - now I am not sure what the
problem is. How can I help you then?

On Wed, Nov 5, 2014 at 1:35 PM, Jha Sonakumar sona@techmahindra.com
wrote:

  We already set the width and height.
  --
 *From:* Filip Piechocki fpiecho...@gmail.com
 *Sent:* Wednesday, November 5, 2014 6:00 PM

 *To:* Jha Sonakumar
 *Cc:* interest@qt-project.org Interest
 *Subject:* Re: [Interest] Regarding auto resizing of the QtQuick window
 for embedded device

  How you know that currently it uses 2000x800?

 On Wed, Nov 5, 2014 at 12:09 PM, Jha Sonakumar sona@techmahindra.com
 wrote:

  Hi Filip

 My display is HD Monitor is 1920X1080,we'd like to connect twin lcd
 displays each of 1280X480. I would like ensure,whether my application
 window will fit to the display or not.

 Currently my application uses widthxheight :(2000x800)

 Is there environment-variable to be set ?


  BR

 SonaKumar


  --
 *From:* Filip Piechocki fpiecho...@gmail.com
 *Sent:* Wednesday, November 5, 2014 4:28 PM

 *To:* Jha Sonakumar
 *Cc:* interest@qt-project.org Interest
 *Subject:* Re: [Interest] Regarding auto resizing of the QtQuick window
 for embedded device

   Like I said - your Window will always be covering whole screen. That's
 how the 'eglfs' plugin works. Why do you want it to cover only a part of
 screen?

 On Wed, Nov 5, 2014 at 11:47 AM, Jha Sonakumar sona@techmahindra.com
  wrote:

  Hi Filip

 i tried with the following code:

 Window {
 visible: true
 width: 1200
 height: 480

 Rectangle{
 id:rect
 color:black
 anchors.fill: parent

 Item {
 anchors.centerIn: parent
 width: 800
 height: 480
 focus:true

 Audio {
 id: player
 source:qrc:/Neela Yevaru.mp3
 autoPlay: true
 muted: false
 }

 Keys.onSpacePressed: playPauseMedia()

 function playPauseMedia(){
 switch(player.playbackState) {
 case Audio.PlayingState:
 player.pause()
 console.log(Paused media)
 break
 case Audio.PausedState:
 player.play()
 console.log(Playing media)
 break
 default:
 break
 }

 }
 }
 }
 }


  still result is same


  BR

 Sona
  --
 *From:* Filip Piechocki fpiecho...@gmail.com
 *Sent:* Wednesday, November 5, 2014 3:36 PM
 *To:* Jha Sonakumar
 *Cc:* interest@qt-project.org Interest

 *Subject:* Re: [Interest] Regarding auto resizing of the QtQuick window
 for embedded device

   That's what I thought as with linuxfb you won't be able to use
 QtQuick 2.x as it requires OpenGL.
 So with 'eglfs' your application is displayed on the whole frame buffer
 and so it covers whole screen. So anything you type as width and height of
 the root element has no meaning as it will be resized to whole screen. I
 you want it smaller then you might wrap your main element with Rectangle.
 Something like this:

  Window {
   Rectangle {
 anchors.fill: parent
 color: black

  Item { // this item is representig the main item of your
 application
   anchors.centerIn: parent
   width: 2560
   height: 480
 }
   }
 }

  You application will stiil be full screen, but the content will be
 resized inside this black rectangle.

 On Wed, Nov 5, 2014 at 10:52 AM, Jha Sonakumar 
 sona@techmahindra.com wrote:

  Hi Filip,


  you are right, i am using eglfs Yocto


  BR

 SonaKumar
  --
 *From:* interest-bounces+sona.jha=techmahindra@qt-project.org
 interest-bounces+sona.jha=techmahindra@qt-project.org on behalf
 of Filip Piechocki fpiecho...@gmail.com
 *Sent:* Wednesday, November 5, 2014 3:18 PM
 *To:* Jha Sonakumar; interest@qt-project.org Interest

 *Subject:* Re: [Interest] Regarding auto resizing of the QtQuick
 window for embedded device



 On Wed, Nov 5, 2014 at 10:32 AM, Jha Sonakumar 
 sona@techmahindra.com wrote:

  sory.. what do u mean by QPA?

 Platform Abstraction plugin. Are you using X11? If yes then you are
 probably using 'xcb' QPA plugin, but I guess you are not using X11, a then
 'eglfs' plugin is what you use, right?


   --
 *From:* interest-bounces+sona.jha=techmahindra@qt-project.org
 interest-bounces+sona.jha=techmahindra@qt-project.org on behalf
 of Filip Piechocki fpiecho...@gmail.com
 *Sent:* Wednesday, November 5, 2014 2:56 PM
 *To:* Jha Sonakumar
 *Cc:* interest

Re: [Interest] How to configure Qt5 for Beaglebone Black

[Filip Piechocki]

First of all you need to decide which QPA plugin you want to use. If you
use Ubuntu on the device then I guess you want to launch your apps in X11,
right (like on desktop)? Then xcb plugin is what you need, so passing
-no-xcb makes no sense. If you rather like to make fullscreen app without
any desktop environment, then eglfs would be sufficient for you, but there
you can have only one window (so things like comboboxes, menus or dialogs
will not work).
Then, I've never built Qt for BBB, but as you are using Ubuntu there I
would probably follow the same steps I do for RaspberryPi. Here is the
tutorial:
https://www.ics.com/blog/building-qt-and-qtwayland-raspberry-pi#.VCO3ZmCSyzc
what is intresting for you it is the list of packages to install on the
target and it is convenient to mount the sysroot via nfs (like it is
described there).

BR,
Filip

On Wed, Sep 24, 2014 at 7:09 PM, Amey Patil amey.pa...@sjsu.edu wrote:

 I am working on a Ubuntu host.
 Trying to configure Qt5 to develop GUI touch applications on Beaglebone
 Black.
 Having a lot of trouble understanding the QPA eglfs openGL ES2.

 My plan is once i configure the Qt5 source, i will copy the libraries to
 Beaglebone Black, cross compile my appication on ubuntu host and then
 execute this application on BBB.
 But, everytime i tweak the configure options, it gives me some error.
 You can review my configure attempts here;

 http://www.epicsqt.org/wiki/QtEverywhere/EmbeddedSystems/BeagleBoneBlack/ConfigureQtForBbb#Configure

 I tried yocto too, but it didn't end up well. No solid resource for that
 too.. :(
 tried yocto from here.
 https://www.ics.com/blog/beaglebone-black-low-cost-embedded-platform-part-3

 For time being want to make the configure thing work.
 Can you please help me with the same.

 Thanks in advance.

 Sincere Regards,
 Amey Uday Patil

 On Wed, Sep 24, 2014 at 9:49 AM, Thiago Macieira 
 thiago.macie...@intel.com wrote:

 On Wednesday 24 September 2014 09:38:36 Amey Patil wrote:
  Hi all,
 
  Searched a lot online.
  Didn't find any working source for configuring Qt5 for Beaglebone Black.

 Tell us what your problem is.

 First of all, are you using a reasonable OS for that device, like a Yocto-
 based one? If so, Yocto has recipes for building Qt 5, please use them.

 If not, please explain why you're not using Yocto or similar.

 --
 Thiago Macieira - thiago.macieira (AT) intel.com
   Software Architect - Intel Open Source Technology Center

 ___
 Interest mailing list
 Interest@qt-project.org
 http://lists.qt-project.org/mailman/listinfo/interest



 ___
 Interest mailing list
 Interest@qt-project.org
 http://lists.qt-project.org/mailman/listinfo/interest


___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] Custom .prf files for QMake in project root?

[Filip Piechocki]

Haven't tested this on Qt5 but on Qt4 we were using:
qmake -set QMAKEFEATURES /path/to/prf/files

and put all prf files in the /path/to/prf/files directory. Main downside of
this is that you have to set this qmake variable - so just shipping custom
prf files is not enough, you have to force the developer to set the proper
path.

BR,
Filip


On Sun, Aug 17, 2014 at 6:23 PM, Elvis Stansvik elvst...@gmail.com wrote:

 Hi folks,

 According to point 3 in the second list at [1], I should be able to put my
 own .prf feature files for QMake in the project root.

 I tried putting my foo.prf in features/win32/foo.prf with a simple
 message(foo.prf loaded) in it, but it was not loaded by QMake.

 I then took a look at the QMake source  and found [2]. It seems that QMake
 will only look for .prf files in the project root if it contains some form
 of cache file. (See also the comment for the linked function.)

 So my question are:

 1) What is this cache file? I can't remember ever seeing that on Linux or
 Windows.
 2) Why is QMake only loading the .prf files in the project root if there's
 a cache file? It seems an arbitrary limitation to me, but perhaps I'm
 missing something?

 AFAICS this makes it impossible to ship custom .prf files with your
 project and rely on them being loaded by QMake :(

 Best regards,
 Elvis Stansvik

 [1]
 http://qt-project.org/doc/qt-5/qmake-advanced-usage.html#adding-new-configuration-features
 [2]
 https://qt.gitorious.org/qt/qt/source/469dcfff3e39249b0a5eb98242fbe5f917587246:qmake/project.cpp#L565-573

 ___
 Interest mailing list
 Interest@qt-project.org
 http://lists.qt-project.org/mailman/listinfo/interest


___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] Help!! app qt4 upgrade to qt5 for wayland on tizen ivi, can't get the QDialog's window handle which can cast to EGLNativeWindowType

[Filip Piechocki]

Hi,
As Giulio wrote, it is not clear what you want to achieve. If you want to
draw with OpenGL on a Qt widget, there is a QGLWidget which is supposed for
that (or its actual replacement - QOpenGLWidget, but it will be introduced
in 5.4 if I'm not wrong here, you can try the latest snapshot). QDialog is
not supposed for that.

BR,
Filip
On Aug 8, 2014 3:57 AM, Steve (YiLiang) Zhou sz...@telecomsys.com wrote:

 Hi Thiago,
 Thanks for your  reply, Giulio did give me some advices to try , but I'm
 not so familiar with qt and wayland ,so I post the help request here
 too.
 Can you or Giulio give me some sample codes so that I can get this work?
 Anyway thank you guys very much for your replys.



 Thanks and Best Regards
 Steve Zhou

 -Original Message-
 From: Thiago Macieira [mailto:thiago.macie...@intel.com]
 Sent: Thursday, August 07, 2014 10:19 PM
 To: interest@qt-project.org
 Cc: Steve (YiLiang) Zhou
 Subject: Re: [Interest] Help!! app qt4 upgrade to qt5 for wayland on
 tizen ivi, can't get the QDialog's window handle which can cast to
 EGLNativeWindowType

 On Thursday 07 August 2014 15:51:31 Steve  Zhou wrote:
  Dear all,

 Hi Steve

 Didn't Giulio reply to you on this very subject on the wayland mailing
 list?
 Giulio is Qt Wayland's co-maintainer, so his answer there is the best
 you're going to get.

 Is there anything new?
 --
 Thiago Macieira - thiago.macieira (AT) intel.com
   Software Architect - Intel Open Source Technology Center


 CONFIDENTIALITY NOTICE: The information contained in this message may be
 privileged and/or confidential. If you are not the intended recipient, or
 responsible for delivering this message to the intended recipient, any
 review, forwarding, dissemination, distribution or copying of this
 communication or any attachment(s) is strictly prohibited. If you have
 received this message in error, please notify the sender immediately, and
 delete it and all attachments from your computer and network.
 ___
 Interest mailing list
 Interest@qt-project.org
 http://lists.qt-project.org/mailman/listinfo/interest

___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] Embedding QWindow

[Filip Piechocki]

According to this blog post:
http://blog.qt.digia.com/blog/2014/07/02/qt-weekly-16-qquickwidget
never use the QWidget::createWindowContainer() :) use QQuickWidget instead.

BR,
Filip


On Tue, Aug 5, 2014 at 10:31 AM, Till Oliver Knoll 
till.oliver.kn...@gmail.com wrote:

 Am 05.08.2014 um 10:27 schrieb Till Oliver Knoll 
 till.oliver.kn...@gmail.com:

  ...
 
  That's exactly the magic keyword here, the static method of
 QWidget::createContainerWidget!

 That's

   QWidget::createWindowContainer()

 to be correct ;)

 Cheers,
   Oliver
 ___
 Interest mailing list
 Interest@qt-project.org
 http://lists.qt-project.org/mailman/listinfo/interest

___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] Embedding QWindow

[Filip Piechocki]

On Tue, Aug 5, 2014 at 1:29 PM, Till Oliver Knoll 
till.oliver.kn...@gmail.com wrote:

 Am 05.08.2014 um 10:48 schrieb Filip Piechocki fpiecho...@gmail.com:

 According to this blog post:
 http://blog.qt.digia.com/blog/2014/07/02/qt-weekly-16-qquickwidget
 never use the QWidget::createWindowContainer() :) use QQuickWidget instead.


 Read the fine print: ;)


That's why I pasted the link to this article - so anybody can read it in
details :)



 having a QQuickView embedded via createWindowContainer() will always lead
 to better performance when compared to QQuickWidget

 The reason is probably related to buffering: according to the blog all
 drawing of the QQuickWidget - that includes (raw) OpenGL drawing as well, I
 guess - will first go into an application specific buffer where it is
 combined with all the other widget paintings (notably transparent
 overlays etc., which otherwise would cause rendering artifacts when
 using native windows).


 That per Qt application buffering (especially referring to raw OpenGL)
 even raises more interesting questions on platforms such as OS X where the
 Window (composition) Manager itself introduces yet another per application
 buffer (so swapping GL double buffers on OS X is in fact pointless,
 since the window manager will do this for you, too).

 So you render into the Qt application buffer, which gets copied into the
 OS specific per application buffer, which eventually (with the whole
 composited desktop) is copied into the video (front) buffer.

 Even more interesting: Retina displays (on OS X). By default the OpenGL
 framebuffer resolution that is created by the OS when requesting a window
 size of w times h points is half the resolution of the Retina display,
 such that the same amount of OpenGL fragments are processed by default,
 as compared to a non-Retina display with the same window size [in points].

 If one really wants to draw with OpenGL in the native (physical)
 resolution then a flag (in Core Graphics?) can be set before creating the
 corresponding OpenGL Cocoa widget.

 Besides the Retina use case there is another full screen with custom
 resolution use case: instead of switching the graphic mode (resolution)
 for full screen OpenGL applications one simply requests a custom size of
 the frame buffer. The window manager itself will then scale up that buffer
 (without the application having to deal with that, apart from initially
 requesting the custom size buffer) to the physical screen resolution.


 I wonder how this all adds up when the application introduces yet another
 per application composition layer with buffer...?


 But yes, there are issues with createWindowContainer ;) (especially on
 certain embedded systems with no Window Manager). But from what I
 understand they are not worse than what we know from QGLWidget (on desktop
 systems anyway).

 And let's just wait what QOpenGLWidget brings to us and how it turns out
 in practise with all this buffering!


 By now it should be clear that if you want to have as few as possible
 between you and the GPU: use QWindow only!



 Cheers,
   Oliver

 ___
 Interest mailing list
 Interest@qt-project.org
 http://lists.qt-project.org/mailman/listinfo/interest


___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

[Interest] QtWebEngine - only white rectangle

[Filip Piechocki]

Hi,

I've just built QtWebEngine with just built Qt 5.3.0 and my WebEngineView
is always white. I've checked all the examples (QtQuick and widgets) and it
is always the same - just white, instead of the page rendered. What is
weird though - I can still click the links on this opened page (e.g. I can
click on downloads on qt-project.org while I see just white page) - so it
looks like it's rendered somewhere but not displayed...

Does anyone had this issue?

BR,
Filip
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] QIcon from ARGB32 data

[Filip Piechocki]

I am really against sharing the working solutions, because you will just
copy-pasted it you will learn nothing so, here is what you have to do
(although I really thought it is clear enough...) - just translate this
recipe to the C++ language.

You have to split the string you pasted once before (as [3]) on the ','
character (see QString::split()) so you get the QStringList containing all
the needed numbers (but theye are kept as STRINGs). Then you have to
iterate over this list (see foreach() ) and convert every string to a
number (see QString::toInt(), I also added  0xff to get the least
significant byte from the int, and static_casted it to uchar type, but I
don't think all of this is neccessary), and append each number to the
QByteArray. Then this byte array contains data you need, so you can use
apropiate QImage constructor (QImage(uchar *data, int width, int height,
QImage::Format format, ...) ) and the rest you already know.

BR,
Filip


On Sat, Jun 14, 2014 at 2:10 PM, Damian Ivanov damianator...@gmail.com
wrote:

 Hello once more,

 Filip would you mind sharing the code with me so you got the flag?
 I tried lots of combinations... Should the data look like [1] ?

 1 http://pastie.org/9289563

___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] QIcon from ARGB32 data

[Filip Piechocki]

You mean you append to byte array the exact string from link [3]?? Then it
is not going to work in any way!
For example the -128 string is a 4 characters so if they are just 8-bit
characters this whole string has 4 bytes, so the '-' would be you alpha,
'1' (not 1, the character '1') would be your red color and so on... Rather
convert it to a values.

BR,
Filip


On Fri, Jun 13, 2014 at 7:52 AM, Damian Ivanov damianator...@gmail.com
wrote:

 Hi Filip,

 Thanks a lot for your answer!
 It well kinda works - an icon is shown but it's garbage, it should not
 be. Is there any information on the internet (I googled) on argb32
 more specifically how it should look like(as byteArray)?
 I'm asking because I am trying to implement a Qt-only(no kde binding)
 StatusNotifier application(1).
 I get via dbus (2) as QString and I kinda chop and cut it so it
 contains (3) which I think should be correct data of an argb32 icon or
 not?

 After that I put (3) into the QByteArray via
 byteArray.append(theChoppedAndCutStringExactlyAsContainedInLink3)
 End at last I do:
 QImage image((uchar *)utf8.constData(), 21, 14, QImage::Format_ARGB32);
 QPixmap pixmap = QPixmap::fromImage(image);
 return QIcon(pixmap) ;

 Thanks for your time and help!
 Damian

 1. http://www.notmart.org/misc/statusnotifieritem/icons.html
 2. http://pastie.org/9285519
 3. http://pastie.org/9285524
 ___
 Interest mailing list
 Interest@qt-project.org
 http://lists.qt-project.org/mailman/listinfo/interest

___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] QIcon from ARGB32 data

[Filip Piechocki]

What is the size of this icon?


On Fri, Jun 13, 2014 at 10:45 AM, Damian Ivanov damianator...@gmail.com
wrote:

 You mean you append to byte array the exact string from link [3]?? Then
 it is not going to work in any way!
 Yes the exact string. I also thought it's strange that there is -128
 (maybe because it is in network byte order over dbus?)

 Rather convert it to a values.
 I don't know how :(
 ___
 Interest mailing list
 Interest@qt-project.org
 http://lists.qt-project.org/mailman/listinfo/interest

___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] QTablewidget Item deletion

[Filip Piechocki]

Hi!

It is written in docs:

Sets the item for the given row and column to item.

The table takes ownership of the item.

So it means its going to free memory occupied by all its items.

BR,
Filip

On Fri, Jun 13, 2014 at 12:13 PM, Ramakanthreddy Kesireddy
ramakanthreddy.kesire...@techmahindra.com wrote:
 Hi,



 I create Qtablewidget items dynamically in a QtWidget project.



 Do I need to delete explicitly Qtablewidget items or the deletion is taken
 care

 by QTablewidget incase ownership lies with it?



 Thanks and Regards,

 Ramakanth


 

 DISCLAIMER:
 This email (including any attachments) is intended for the sole use of the
 intended recipient/s and may contain material that is CONFIDENTIAL AND
 PRIVATE COMPANY INFORMATION. Any review or reliance by others or copying or
 distribution or forwarding of any or all of the contents in this message is
 STRICTLY PROHIBITED. If you are not the intended recipient, please contact
 the sender by email and delete all copies; your cooperation in this regard
 is appreciated.

 
 
 Disclaimer: This message and the information contained herein is proprietary
 and confidential and subject to the Tech Mahindra policy statement, you may
 review the policy at http://www.techmahindra.com/Disclaimer.html externally
 http://tim.techmahindra.com/tim/disclaimer.html internally within
 TechMahindra.
 


 ___
 Interest mailing list
 Interest@qt-project.org
 http://lists.qt-project.org/mailman/listinfo/interest

___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] QIcon from ARGB32 data

[Filip Piechocki]

You have to extract the data from the string. The string -128 is not
equal the number -128 - it is a basic knowledge you have to understand
even before writing your first hello_world.
You have to split the string on the coma character and then convert
substrings with toInt(), cast to uchar and append to byte array.

Is this icon looking like a flag (dark blue checkerd rectangle in the
left top corner)? Because this is what I got from this string.

BR,
Filip

On Fri, Jun 13, 2014 at 10:52 AM, Damian Ivanov damianator...@gmail.com wrote:
 21x14
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] Performance of platform wayland vs. eglfs

[Filip Piechocki]

Hi,
I didn't test performance with wayland on iMX6, but I had an issue
that when using eglfs I still could see the blinking cursor behind
the qt application (it seemed that the console fb and my app fb are
displayed in paralel) - did you notice something like this? I didn't
resolve this problem and I don't have access to iMX6 board anymore,
but I thought that there might some blitting or something which has an
impact on performance. And what I found I had a bit better performance
(Qt Cinematic Experience is my benchmark) on RasperryPi than on i.MX6
DualLite (wandboard-dual) - both eglfs.

BR,
Filip

On Fri, Jun 13, 2014 at 5:23 PM, Martin Ertl qsmokeonthewa...@gmail.com wrote:
 Hello,

 I compiled an application (see end of this mail) once with Qt 5.0.2 using
 wayland
 plugin and once with Qt 5.3.0 using eglfs plugin.

 Both applications were executed on the same hardware (IMX6).

 The old Qt with wayland results in ~60fps while the new Qt using
 eglfs just reaches 40-45 fps (measured by counting
 QQuickWindow::frameSwapped signals
 in both cases).

 I'd like to understand the difference. I expected it the other way around.
 This is what I assumed:
 When using wayland a surface for a window has to be created and Qt renders
 to that window. Once an image is complete the wayland surface is copied
 to the framebuffer:

 |--|  |--|
 App -draw- | win  | -copy-  |  fb  | -copy- Display
 |--|  |--|

 I expected the eglfs to draw directly to the framebuffer without the need
 for an additional copy from a window. So I expected better performance...

 But my results show that this is not the case. Is the eglfs plugin
 introducing
 some extra overhead?


 Btw.: I had to set 'QT_EGLFS_IMX6_NO_FB_MULTI_BUFFER' to '1'. Otherwise
 there's a segmentation fault.
 gdb prints something about 'libGAL' and 'gcoOS_SynchronousFlip' which seems
 to be something from
 the graphics driver. Could this be a reason for lower eglfs performance?

 Thank you and best regards,
 Martin

 main.cpp: from hello world example, but setting Qt::FramelessWindowHint
 to viewer.

 start MyCompo.qml:
 import QtQuick 2.0

 Rectangle
 {
 id: root
 property color c0
 property color c1


 anchors.fill: parent
 color: yellow


 SequentialAnimation on color
 {
 running: true
 loops: Animation.Infinite

 ColorAnimation {to: root.c0; duration: 1000}
 ColorAnimation {to: root.c1; duration: 1000}
 }
 }
 end MyCompo.qml:

 start main.qml:

 import QtQuick 2.0
 import Ces.Generic 1.0

 Item
 {
 width: 640
 height: 640


 Text
 {
 x: 10
 y: 10
 font.pixelSize: 20
 color: white
 text: fps.fps2
 z: 1

 CGFPSCounter
 {
 id: fps
 }
 }

 MyCompo
 {
 c0: red
 c1: green
 }
 MyCompo
 {
 c0: red
 c1: blue
 opacity: 0.5
 }
 MyCompo
 {
 c0: red
 c1: blue
 opacity: 0.5
 }
 MyCompo
 {
 c0: red
 c1: blue
 opacity: 0.5
 }
 MyCompo
 {
 c0: red
 c1: blue
 opacity: 0.5
 }
 MyCompo
 {
 c0: red
 c1: blue
 opacity: 0.5
 }
 MyCompo
 {
 c0: red
 c1: blue
 opacity: 0.5
 }
 MyCompo
 {
 c0: red
 c1: blue
 opacity: 0.5
 }
 MyCompo
 {
 c0: red
 c1: blue
 opacity: 0.5
 }
 MyCompo
 {
 c0: red
 c1: blue
 opacity: 0.5
 }
 MyCompo
 {
 c0: red
 c1: blue
 opacity: 0.5
 }
 MyCompo
 {
 c0: red
 c1: blue
 opacity: 0.5
 }
 MyCompo
 {
 c0: red
 c1: blue
 opacity: 0.5
 }
 }

 end main.qml:


 ___
 Interest mailing list
 Interest@qt-project.org
 http://lists.qt-project.org/mailman/listinfo/interest

___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] QIcon from ARGB32 data

[Filip Piechocki]

Hu


On Fri, Jun 13, 2014 at 12:00 AM, Damian Ivanov damianator...@gmail.com
wrote:

 Hello,

 I'm trying to show a QIcon from ARGB32 data which come from dbus,


Okay, so this means that you have raw pixel data, yes?


 any help suggestions how to do that?

 I have a QByteArray which contains the data, I tried

 QImage image;
 image.loadFromData(myByteArray);


and if you have raw pixel data, than using loadFromData() is not right as
you might read the docs and they say:
The loader attempts to read the image using the specified format, e.g.,
PNG or JPG. If format is not specified (which is the default), the loader
probes the file for a header to guess the file format.

The file format is JPG, PNG, BMP and ARGB32 is the image format. All those
file formats can store the image with this given image format. So you need
to know the width and height of the image and use:

QImage image(myByteArray.constData(), width, height, QImage::Format_ARGB32);

Note that the data has to live as long as QImage and all it's undetached
copies.

Then you can use the code below.


 QPixmap pixmap = QPixmap::fromImage(image);

return QIcon(pixmap) ;
 unfortunately this doesn't show the icon.

 Thanks in advance.
 Damian


BR,
Filip


 ___
 Interest mailing list
 Interest@qt-project.org
 http://lists.qt-project.org/mailman/listinfo/interest

___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] QIcon from ARGB32 data

[Filip Piechocki]

On Jun 13, 2014 5:58 AM, Filip Piechocki fpiecho...@gmail.com wrote:

 Hu

That was supposed to be Hi :)



 On Fri, Jun 13, 2014 at 12:00 AM, Damian Ivanov damianator...@gmail.com
wrote:

 Hello,

 I'm trying to show a QIcon from ARGB32 data which come from dbus,


 Okay, so this means that you have raw pixel data, yes?


 any help suggestions how to do that?

 I have a QByteArray which contains the data, I tried

 QImage image;
 image.loadFromData(myByteArray);


 and if you have raw pixel data, than using loadFromData() is not right as
you might read the docs and they say:
 The loader attempts to read the image using the specified format, e.g.,
PNG or JPG. If format is not specified (which is the default), the loader
probes the file for a header to guess the file format.

 The file format is JPG, PNG, BMP and ARGB32 is the image format. All
those file formats can store the image with this given image format. So you
need to know the width and height of the image and use:

 QImage image(myByteArray.constData(), width, height,
QImage::Format_ARGB32);

 Note that the data has to live as long as QImage and all it's undetached
copies.

 Then you can use the code below.


 QPixmap pixmap = QPixmap::fromImage(image);

 return QIcon(pixmap) ;
 unfortunately this doesn't show the icon.

 Thanks in advance.
 Damian


 BR,
 Filip


 ___
 Interest mailing list
 Interest@qt-project.org
 http://lists.qt-project.org/mailman/listinfo/interest


___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] [QML] How to create a sub Window for Window {...}

[Filip Piechocki]

So just use Rectangle :) or Item if you just want an empty item, or
Component to load some QML from file.

BR,
Filip Piechocki


On Mon, Jun 2, 2014 at 9:51 AM, Yuchen Deng loa...@gmail.com wrote:

 Actually, I don't really want an MDI interface. I just want load or open
 another qml as child Window show inside the parent.
 like this (using QML's Rectangle):
 http://picpaste.com/sub-window-y43R1Kuf.png
 not like this (using QML's Window):
 http://picpaste.com/no-sub-window-Jq7qeOu5.png



 2014-06-02 14:54 GMT+08:00 Rutledge Shawn shawn.rutle...@digia.com:

 What do you mean by sub window?  If you mean you are trying to create an
 MDI interface, with a window acting as a desktop and having more windows
 inside, that's not supported in Qt Quick and is unlikely at this point,
 since the widgets implementation turned out to be quite bug-prone, and MDI
 has anyway mostly fallen out of fashion.  When you declare a Window inside
 a Window, it becomes transient for the outer window: a hint is given to
 the window manager that they are related to each other, so usually it will
 be shown centered over its transient parent.

 On 1 Jun 2014, at 1:25 PM, Yuchen Deng wrote:

  hi, list! I have to ask for help because I can't create an sub window
 on Window {...}.
  I've tried some days, after Google still can't solved my problem.
 
  main.qml
  import QtQuick 2.2
  import QtQuick.Window 2.1
  Window {
  id: mainWindow
  visible: true
  width: 760; height: 520
  color: red
  property variant win;  // you can hold this as a reference..
  Text {
  text: Click here to open sub window 2!
  anchors.centerIn: parent
  }
  Window {
  id: subWindow_1
  width: 555
  height: 333
  visible: true
  flags: Qt.SubWindow
  }
  MouseArea {
  anchors.fill: parent
  onClicked: {
  var component = Qt.createComponent(subwindow2.qml);
  win = component.createObject(mainWindow);
  win.show();
  }
  }
  }
 
  subwindow2.qml
  import QtQuick 2.2
  import QtQuick.Window 2.1
  Window {
  id: subWindow_2
  visible: true
  width: 500; height: 300
  color: blue
  flags: Qt.SubWindow
  Rectangle {
  anchors.fill: parent
  color: lightGrey
  Text {
  anchors.centerIn: parent
  text: Sub Window 2
  }
  }
  }
 
 
  See the code, it's can open two window, But can't open as sub window in
 parent.
  Any help / tips are very welcome!
  Thanks you!
  --
  Best Regards
  Yuchen
  ___
  Interest mailing list
  Interest@qt-project.org
  http://lists.qt-project.org/mailman/listinfo/interest




 --
 Best Regards
 Yuchen

 ___
 Interest mailing list
 Interest@qt-project.org
 http://lists.qt-project.org/mailman/listinfo/interest


___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] How to switch two Qt applications on Embedded Linux ?

[Filip Piechocki]

Do you have any window manager on your embedded device? What QPA plugin do
you use on your embedded device?

BR,
Filip Piechocki


On Mon, May 26, 2014 at 11:34 AM, Xubao Jiang jiangxu...@gmail.com wrote:

 Hi all,

 I meet an problem about switch two Qt applications on my Embedded Linux
 soc.

 I have written an application Launcher, which will start other
 applications using QProcess. It calls hide() when the new app start, and
 calls show() when the new app is closed. This works normally.

 Now I want to the two applications can be alive at the same time. I tried
 to call hide() in the new app, and then send messages(D-Bus) to Launcher.
 When Launcher receives this message, it will call show(). But Launcher
 didn't show again, and the screen is black. After debugging, Launcher did
 receive the message and show() is called. I don't know why it doesn't
 display again.

 This method works normally on Ubuntu pc. I want to know if Qt embedded
 supports this feature or not? My Qt version is 5.0.2.

 One work round is to write one application to do all work, but it seems
 too complicated. Does anyone have met the same issue before? What is your
 solution for application management? Is one application the general
 solution for this?


 Best regards,
 Xubao

 ___
 Interest mailing list
 Interest@qt-project.org
 http://lists.qt-project.org/mailman/listinfo/interest


___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] BUG? QTimer in QThread

[Filip Piechocki]

Looks like Andre was a little bit faster to point this out.

BR,
Filip Piechocki


On Tue, May 13, 2014 at 2:03 PM, Filip Piechocki fpiecho...@gmail.comwrote:

 I would like to mention, that in the first email the thread is never
 started and without starting the thread I would not expect much to happen
 in this thread :)

 BR,
 Filip Piechocki


 On Tue, May 13, 2014 at 2:00 PM, Mandeep Sandhu 
 mandeepsandhu@gmail.com wrote:

  Thanks Mandeep, the problem was caused by the timer starting in the
  constructor and then moved by moveToThread, as André pointed out. I
 don't
  really understand why is it so, but well, it works :)

 I'm glad it worked for you, although the example I sent you starts the
 timer in the c'tor only (and later moveTothread is called) and still
 works. Could it be a Qt-on-Mac issue (maybe you can compile my example
 on your setup and test)?

 -mandeep

 
 
  Thanks!
 
 ___
 Interest mailing list
 Interest@qt-project.org
 http://lists.qt-project.org/mailman/listinfo/interest



___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] Accessing a QML object, via constructed id in JavaScript

[Filip Piechocki]

Hi Eric,

What is the reason you can't use it like this:

if (english_weight1.checked)


but instead you are refering to the item by name? Maybe your mistake
is with the construction you are using?


BR,

Filip




On Tue, Apr 15, 2014 at 6:50 AM, Eric Feigenson e...@feigenson.net wrote:

 Hello all...

 I'm writing some JavaScript code inside QML.  What I'd like to do is be
 able to access an object via id where the id is in a JavaScript string.

 For example, given the QML:

 CheckBox {

 id: english_weight1

 text: qsTr(2.5 lb)

 }


 and the JavaScript fragment:

 var idName = english_weight1;

 if (idName.checked)

 // do something is the box is checked...


 But I want the idName in the if statement to refer to the *value* of
 the JavaScript variable idName, in other words,
 english_weight1.checked. I believe I could use eval:

 if (eval(idname + .checked)) ...


 but everything I've read says eval is to be avoided.

 If it helps or makes any difference, the CheckBox is in a Column with id
 myColumn.  I was thinking something like
 myColumn[idName] would do the trick, but I'm only guessing.

 I hope this is a clear enough description... please let me know if any
 more details are needed.

 Any thoughts?

 Thanks!

 -Eric

 ___
 Interest mailing list
 Interest@qt-project.org
 http://lists.qt-project.org/mailman/listinfo/interest


___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] Insert without scrolling

[Filip Piechocki]

Hi Hugo,

The text edit does not scroll up - it is rather your pasted text which
pushes other lines down, while the current scroll stands still. So if you
want to see exactly the same content as before pasting than you need to
scroll down same amount of lines that have been inserted.

Best regards,
Filip


On Thu, Apr 10, 2014 at 11:29 AM, Hugo Teso dixiefl...@gmail.com wrote:

 Hi Tony,

 It did partially. Now, instead of scrolling to the top of the document,
 it scrolls up the same amount of lines that have been inserted.

 I tried to prevent this new scroll but with no success yet. Any ideas?

 Thanks,

 On 10/04/14 03:05, Tony Rietwyk wrote:
  Hi Hugo,
 
  Try using an explicit QTextCursor rather than the QTextEdit interfaces.
 
  Hope that helps,
 
  Tony
 
 
  -Original Message-
  Sent: Thursday, 10 April 2014 2:23 AM
 
  Hi,
 
  I am trying to insert some text at the top of a QPlainTextEdit. To do so
  I'm am
  using this lines of code:
 
  ui-textEdit-moveCursor(QTextCursor::Start, QTextCursor::MoveAnchor);
  ui-textEdit-insertPlainText(Some text here);
 
  The problem is that, by doing this, the textEdit is scrolled to the top
 in
  order
  to show the new inserted text.
 
  Is there any way to avoid this scrolling to the top? I need to insert
 this
  text
  silently without the user noticing.
 
  Thanks for your help,
 
 
  ___
  Interest mailing list
  Interest@qt-project.org
  http://lists.qt-project.org/mailman/listinfo/interest
 
 ___
 Interest mailing list
 Interest@qt-project.org
 http://lists.qt-project.org/mailman/listinfo/interest

___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] Compile a console app for the Raspberry Pi

[Filip Piechocki]

or here: http://www.ics.com/blog/building-qt-5-raspberry-pi#.U0aHm3WSxIM

BR,
Filip


On Thu, Apr 10, 2014 at 2:08 PM, Mandeep Sandhu mandeepsandhu@gmail.com
 wrote:

 Have you tried the instructions here?

 http://qt-project.org/wiki/RaspberryPi_Beginners_guide

 HTH,
 -mandeep


 On Thu, Apr 10, 2014 at 5:14 PM, Petko Ditchev pditc...@gmail.com wrote:
Hello everyone, I thinking now about how to approach the problem in
  the title. I have a small console app (a filter for mic input) that uses
  Qt libs, and I want to deploy it on the Pi. It uses some Qt5 features so
  Qt4 from the repos isn't an option. I was thinking about building it
  statically, but I'm not sure what the steps for that are (on ARM). So is
  that the process :
  1.Cross-compile Qt5 libs (with --static) to be compatible with the RPi
 CPU.
  2.Build the app with that Qt lib.
  3.Deploy to the Pi
  4.Benefit
 
  Or am I missing something?
 
  Petko
  ___
  Interest mailing list
  Interest@qt-project.org
  http://lists.qt-project.org/mailman/listinfo/interest
 ___
 Interest mailing list
 Interest@qt-project.org
 http://lists.qt-project.org/mailman/listinfo/interest

___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] QML Gridview cell's

[Filip Piechocki]

Hi,
I suggest you implement filtering proxy model which will be between
GridView and you model. Then you should use this filtering model in the
GridView. To create your filtering model subclass QSortFilterProxyModel and
reimplement filterAcceptsRow(). You can either prepare a new QML type (so
you can reuse it in the future):

GridView {
model: MyFilteringModel { sourceModel: myPlugin.stringList }
// ...
}

Or just expose instance with your string list model set as a source model:

GridView {
model: myPlugin.filteredStringList
// ...
}

Best Regards,
Filip


On Mon, Mar 3, 2014 at 8:06 AM, Damian Ivanov damianator...@gmail.comwrote:

 Hi all,

 I have a GridView which gets the model from a QStringlist model from c++
 GridView{... model:myPlugin.stringList;...}

 Now this QStringList may contain by nature duplicates.
 Is there a way I can hide them in the GridView?
 I tried in the delegate to set the item visible=false, this hides the
 item but the cell for it is still reserved and makes and empty cell,
 is it possible to hide/destroy this particular cell?

 Thanks in advance!!
 Damian
 ___
 Interest mailing list
 Interest@qt-project.org
 http://lists.qt-project.org/mailman/listinfo/interest

___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] Fonts not rendered properly on RaspberryPi

[Filip Piechocki]

I am using Poky from dora branch.
I've updated freetype and fontconfig to the latest versions (freetype
2.5.2, fontconfig 2.11.0) from poky master but still no success :( which is
weird as I used poky master some time ago and it was working (but it is
hard to use master branch as it is not building for me usually :/).

Any other ideas? Should I report a bug in Qt?

Best regards,
Filip Piechocki


On Mon, Feb 24, 2014 at 8:35 AM, Rutledge Shawn shawn.rutle...@digia.comwrote:


 On 23 Feb 2014, at 9:37 PM, Thiago Macieira wrote:

  Em dom 23 fev 2014, às 20:44:16, Filip Piechocki escreveu:
  For me it looks good, maybe there is something wrong with fontconfig or
  freetype?
 
  That's my guess, yes.

 FWIW I saw this problem too when experimenting with Qt on Wayland on Arch
 Linux, without anything related to X11 being installed (but with fontconfig
 and freetype).  I didn't figure it out yet.  But the packages for Raspbian
 were OK last time I tried.

 http://twolife.be/raspbian/

 ___
 Interest mailing list
 Interest@qt-project.org
 http://lists.qt-project.org/mailman/listinfo/interest

___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] Fonts not rendered properly on RaspberryPi

[Filip Piechocki]

Okay... seems that I found te cause - there are no fonts installed on my
system. How to force Qt to install qtbase/lib/fonts somewhere?

Best Regards,
Filip Piechocki


On Wed, Feb 26, 2014 at 11:55 AM, Filip Piechocki fpiecho...@gmail.comwrote:

 I am using Poky from dora branch.
 I've updated freetype and fontconfig to the latest versions (freetype
 2.5.2, fontconfig 2.11.0) from poky master but still no success :( which is
 weird as I used poky master some time ago and it was working (but it is
 hard to use master branch as it is not building for me usually :/).

 Any other ideas? Should I report a bug in Qt?

 Best regards,
 Filip Piechocki


 On Mon, Feb 24, 2014 at 8:35 AM, Rutledge Shawn 
 shawn.rutle...@digia.comwrote:


 On 23 Feb 2014, at 9:37 PM, Thiago Macieira wrote:

  Em dom 23 fev 2014, às 20:44:16, Filip Piechocki escreveu:
  For me it looks good, maybe there is something wrong with fontconfig or
  freetype?
 
  That's my guess, yes.

 FWIW I saw this problem too when experimenting with Qt on Wayland on Arch
 Linux, without anything related to X11 being installed (but with fontconfig
 and freetype).  I didn't figure it out yet.  But the packages for Raspbian
 were OK last time I tried.

 http://twolife.be/raspbian/

 ___
 Interest mailing list
 Interest@qt-project.org
 http://lists.qt-project.org/mailman/listinfo/interest



___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

[Interest] Fonts not rendered properly on RaspberryPi

[Filip Piechocki]

Hi,

I've built yocto poky (dora branch) for my Raspberry Pi and then
crosscompiled Qt 5.2.1 sources for it (I use eglfs QPA plugin). For test
and benchmark I use Qt Cinematic Experience. Everything is working fine
except fonts. In the cinematic experience no text is visible at all and i
get tons of lines:

Warning: distance-field glyph is not available with index 0

on the console.

When I launched qmlscene without any parameters I got the open file dialog
but all the characters are just squares. I achieved the same result in
cinematic experience by setting QML_DISABLE_DISTANCEFIELD=1.


Any idea whats causing this problem?

Best regards,
Filip Piechocki
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] Fonts not rendered properly on RaspberryPi

[Filip Piechocki]

My config.summary looks like this:


   Configure summary

Building on:   linux-g++ (x86_64, CPU features: mmx sse sse2)
Building for:  devices/linux-rasp-pi-g++ (arm, CPU features:)
Platform notes:

- Also available for Linux: linux-kcc linux-icc linux-cxx

qmake vars .. styles += mac fusion windows DEFINES += QT_NO_MTDEV
QT_CFLAGS_DBUS =
-I/home/faldzip/RaspberryPi/yocto/poky-dora/build/tmp/sysroots/raspberrypi/usr/include/dbus-1.0
-I/home/faldzip/RaspberryPi/yocto/poky-dora/build/tmp/sysroots/raspberrypi/usr/lib/dbus-1.0/include
  QT_LIBS_DBUS = -ldbus-1   QT_CFLAGS_GLIB = -pthread
-I/home/faldzip/RaspberryPi/yocto/poky-dora/build/tmp/sysroots/raspberrypi/usr/include/glib-2.0
-I/home/faldzip/RaspberryPi/yocto/poky-dora/build/tmp/sysroots/raspberrypi/usr/lib/glib-2.0/include
  QT_LIBS_GLIB = -pthread -lgthread-2.0 -lglib-2.0   QT_CFLAGS_PULSEAUDIO =
-D_REENTRANT
-I/home/faldzip/RaspberryPi/yocto/poky-dora/build/tmp/sysroots/raspberrypi/usr/include/glib-2.0
-I/home/faldzip/RaspberryPi/yocto/poky-dora/build/tmp/sysroots/raspberrypi/usr/lib/glib-2.0/include
  QT_LIBS_PULSEAUDIO = -lpulse-mainloop-glib -lpulse -lglib-2.0
QMAKE_CFLAGS_FONTCONFIG =
-I/home/faldzip/RaspberryPi/yocto/poky-dora/build/tmp/sysroots/raspberrypi/usr/include/freetype2
  QMAKE_LIBS_FONTCONFIG = -lfontconfig -lfreetype   QMAKE_INCDIR_LIBUDEV =
  QMAKE_LIBS_LIBUDEV = -ludev -lrt   DEFINES += QT_NO_XCB
QMAKE_CFLAGS_XKBCOMMON =   QMAKE_LIBS_XKBCOMMON = -lxkbcommon
QMAKE_VERSION_XKBCOMMON = 0.3.1 sql-drivers =  sql-plugins =  sqlite qmake
switches .

Build options:
  Configuration .. accessibility alsa audio-backend c++11
clock-gettime clock-monotonic compile_examples concurrent cross_compile
dbus egl eglfs evdev eventfd fontconfig full-config getaddrinfo getifaddrs
glib iconv icu inotify ipv6ifname large-config largefile libudev linuxfb
medium-config minimal-config mremap neon nis no-harfbuzz opengl opengles2
openssl pcre png posix_fallocate precompile_header pulseaudio qpa qpa
reduce_exports reduce_relocations release rpath shared small-config
system-freetype system-zlib xlib
  Build parts   libs
  Mode ... release
  Using C++11  yes
  Using PCH .. yes
  Target compiler supports:
iWMMXt/Neon .. no/yes

Qt modules and options:
  Qt D-Bus ... yes (loading dbus-1 at runtime)
  Qt Concurrent .. yes
  Qt GUI . yes
  Qt Widgets . yes
  JavaScriptCore JIT . yes (To be decided by JavaScriptCore)
  QML debugging .. yes
  Use system proxies . no

Support enabled for:
  Accessibility .. yes
  ALSA ... yes
  CUPS ... no
  FontConfig . yes
  FreeType ... system
  Iconv .. yes
  ICU  yes
  Image formats:
GIF .. yes (plugin, using bundled copy)
JPEG . yes (plugin, using bundled copy)
PNG .. yes (in QtGui, using bundled copy)
  Glib ... yes
  GTK theme .. no
  Large File . yes
  mtdev .. no
  Networking:
getaddrinfo .. yes
getifaddrs ... yes
IPv6 ifname .. yes
OpenSSL .. yes (loading libraries at run-time)
  NIS  yes
  OpenGL . yes (OpenGL ES 2.x)
  OpenVG . no
  PCRE ... yes (bundled copy)
  pkg-config . yes
  PulseAudio . yes
  QPA backends:
DirectFB . no
EGLFS  yes
KMS .. no
LinuxFB .. yes
XCB .. no
  Session management . yes
  SQL drivers:
DB2 .. no
InterBase  no
MySQL  no
OCI .. no
ODBC . no
PostgreSQL ... no
SQLite 2 . no
SQLite ... yes (plugin, using bundled copy)
TDS .. no
  udev ... yes
  xkbcommon .. yes (system library)
  zlib ... yes (system library)

NOTE: Qt is using double for qreal on this system. This is binary
incompatible against Qt 5.1.
Configure with '-qreal float' to create a build that is binary compatible
with 5.1.




For me it looks good, maybe there is something wrong with fontconfig or
freetype?

Best Regards,
Filip Piechocki


On Sun, Feb 23, 2014 at 6:55 PM, Thiago Macieira
thiago.macie...@intel.comwrote:

 Em dom 23 fev 2014, às 09:13:55, Filip Piechocki escreveu:
  Any idea whats causing this problem?

 Check your config.summary in the build and see if there are no items
 where
 you should have yes. As a general rule, you want to have yes everywhere,
 except where you know for sure that you don't need the feature.

 Fonts, in this case.
 --
 Thiago Macieira - thiago.macieira (AT) intel.com
   Software Architect