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
That's not complete because my app isn't listed! ;-)
Mine neither.
Ok, ok... it is only 'in' since yesterday:
https://play.google.com/store/apps/details?id=com.greenflowsolutions.gemote
I must add: I am learning native Android for roughly a week now. Gui development
and configuration with
Hi.
I want to determine how much pixels in 10 mm.
I use the next calculations:
static const qreal fingerSize = 0.0393700787 * 10;
static const qreal h = (qreal) QApplication::desktop()-physicalDpiY() *
fingerSize;
And this calculations return to me 28 that on my desktop is 5 mm only.
igor.mironc...@gmail.com schreef op 23-2-2014 13:24:
Hi.
I want to determine how much pixels in 10 mm.
I use the next calculations:
staticconstqrealfingerSize=0.0393700787*10;
staticconstqrealh=
(qreal)QApplication::desktop()-physicalDpiY()*fingerSize;
And this calculations return to me 28
I'd say there's no 100% reliable cross-platform solution and Qt can't do
anything about it — the screen itself may return incorrect information
about its physical size, OS may somehow misinterpret that information or
simply fake it by reversing the calculations (i.e. calculate physical
size by
On Sunday 23 February 2014, igor.mironc...@gmail.com wrote:
I’m absolutely sure that Qt determines DPI wrong.
I’ve received from Qt that my screen has 72 DpiY, where actually it has
130.
So my question is what can I use else then QDesktopIWidget::physicalDpiY()?
I find
On Sunday 23 February 2014, igor.mironc...@gmail.com wrote:
QScreen::physicalDotsPerInch returns the same value as
QDesktopWidget::physicalDpi.
But why do you think that QScreen::physicalDotsPerInch more reliable?
P.S. I did not look at the Qt code yet, but I guess that I have to do it...
You are right.
QScreen is more reliable than QDesktopWidget.
At least QScreen makes calculations, handles system's calls, etc...
-Original Message-
From: Allan Sandfeld Jensen
Sent: Sunday, February 23, 2014 4:54 PM
To: igor.mironc...@gmail.com
Cc: interest@qt-project.org ; Andre
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
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 ..
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.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
Le 02/01/2014 22:14, Jason H a écrit :
The list doubled from yesterday to today!
-
*From:* Jonathan Greig redteam...@gmail.com
*To:* Дмитрий Козлов gni...@mail.ru
*Cc:* Interests Qt
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
13 matches
Mail list logo
