On 03.12.2013 10:28, Thomas Hartmann wrote:
There will be no design/welcome page everybody likes. What we can
provide is a welcome page that works for everybody and does not get into
the way.
I present an alternative, with a clearly defined feature set and without
room for bikeshedding (*):
@qt-project.org] p#229; vegne av
Thiago Macieira [thiago.macie...@intel.com]
Sendt: 3. desember 2013 18:09
To: development@qt-project.org
Emne: Re: [Development] OpenGL drivers
On terça-feira, 3 de dezembro de 2013 10:27:24, Thomas Hartmann wrote:
Hi,
we really should think about
@qt-project.org
[development-bounces+gunnar.sletta=digia@qt-project.org] p#229; vegne av
Thiago Macieira [thiago.macie...@intel.com]
Sendt: 3. desember 2013 18:09
To: development@qt-project.org
Emne: Re: [Development] OpenGL drivers
On terça-feira, 3 de dezembro de 2013 10:27:24, Thomas
2013 18:09
To: development@qt-project.org
Emne: Re: [Development] OpenGL drivers
On terça-feira, 3 de dezembro de 2013 10:27:24, Thomas Hartmann wrote:
Hi,
we really should think about introducing em or percent for font sizes.
But non pixel size fonts create a lot of problems for complex
On 04 Dec 2013, at 11:47, Sletta Gunnar gunnar.sle...@digia.com wrote:
QWidget has the exact opposite problem. Layouts, styles and rendering happens
in pixel units while fonts are sized in point size. This is also a problem
when moving between platfoms as the pixelsize of a point has a
Macieira [thiago.macie...@intel.com]
Sendt: 3. desember 2013 18:09
To: development@qt-project.org
Emne: Re: [Development] OpenGL drivers
On terça-feira, 3 de dezembro de 2013 10:27:24, Thomas Hartmann wrote:
Hi,
we really should think about introducing em or percent for font sizes.
But non
.
Fra: Mark Gaiser [mark...@gmail.com]
Sendt: 4. desember 2013 14:54
To: Curtis Mitch
Cc: Sletta Gunnar; Thiago Macieira; development@qt-project.org
Emne: Re: [Development] OpenGL drivers
On Wed, Dec 4, 2013 at 12:37 PM, Mitch Curtis mitch.cur...@digia.com wrote
Hi,
On Wednesday 04 December 2013 11:47:29 Sletta Gunnar wrote:
If we added conversion functions for inch(), cm(), mm(), points() to
QQuickItem, it could look up its current window/screen object and figure
out the relationship between each unit for the screen the item is on and
just set that.
Hi,
the design was done by a professional designer.
I am not a professional designer and so far I trusted external
expertise. I did some sanity checks of course and other software
products use even smaller fonts.
Using pixel size is problematic, but using point sizes is not perfect
either.
Hi,
we really should think about introducing em or percent for font sizes.
But non pixel size fonts create a lot of problems for complex layouts.
This is a general problem mostly of the web world, but also relevant
to webish QML like the welcome page.
There is no general solution. You use px
On terça-feira, 3 de dezembro de 2013 10:27:24, Thomas Hartmann wrote:
Hi,
we really should think about introducing em or percent for font sizes.
But non pixel size fonts create a lot of problems for complex layouts.
QWidget has worked with that for 15 years, so I don't accept that as an
On Nov 30, 2013, at 10:29 PM, Mark Gaiser mark...@gmail.com wrote:
On Fri, Nov 29, 2013 at 7:01 PM, Thiago Macieira
thiago.macie...@intel.com wrote:
On sexta-feira, 29 de novembro de 2013 12:27:44, Sletta Gunnar wrote:
So, I'm asking that if you encounter issues with flickering, crashes, bad
Just use this where you need native looking text:
Having to put that everywhere a Text {} element is used in a
cross-platform app is ugly. One could wrap this in a custom component
but it shouldn't be necessary for such a basic use case.
Regards,
Rob.
On 2 December 2013 11:11, Ziller Eike
Hi,
the Controls have a Label item.
Kind Regards,
Thomas Hartmann
Am 02/12/2013 13:41, schrieb Robert Knight:
Just use this where you need native looking text:
Having to put that everywhere a Text {} element is used in a
cross-platform app is ugly. One could wrap this in a custom component
Hi,
yes, this was a conscious decision. Does it create usability issues for you?
Kind Regards,
Thomas Hartmann
Am 01/12/2013 03:30, schrieb Thiago Macieira:
On sábado, 30 de novembro de 2013 22:29:12, Mark Gaiser wrote:
What you refer to are probably the fonts rendered through QML. By
On Dec 2, 2013, at 4:44 PM, Thiago Macieira thiago.macie...@intel.com wrote:
On segunda-feira, 2 de dezembro de 2013 14:26:29, Thomas Hartmann wrote:
Hi,
yes, this was a conscious decision. Does it create usability issues for you?
Usability? That's debatable. My eyesight is still pretty
On 2 December 2013 16:44, Thiago Macieira thiago.macie...@intel.com wrote:
The project names and paths have blurry fonts because
they're way too small.
Not to mention the totally broken kernings on the bigger texts (the
buttons and the New to Qt area)... :(
--
Giuseppe D'Angelo
yes, this was a conscious decision. Does it create usability issues for you?
Digia is trying to sell a UI toolkit for native app development.
Surely you want one of Qt's flagship apps to create a good first
impression!
On 2 December 2013 16:32, Giuseppe D'Angelo dange...@gmail.com wrote:
On 2
On segunda-feira, 2 de dezembro de 2013 16:28:06, Ziller Eike wrote:
On Dec 2, 2013, at 4:44 PM, Thiago Macieira thiago.macie...@intel.com
wrote:
On segunda-feira, 2 de dezembro de 2013 14:26:29, Thomas Hartmann wrote:
Hi,
yes, this was a conscious decision. Does it create usability
On sábado, 30 de novembro de 2013 22:29:12, Mark Gaiser wrote:
What you refer to are probably the fonts rendered through QML. By
default QML renders fonts with the distance field stuff [1]. It
looks awesome on mobile, but looks horrible on the desktop. This has
been known for a while [2] but
On 30/11/2013 21:29, Mark Gaiser wrote:
On Fri, Nov 29, 2013 at 7:01 PM, Thiago Macieira
thiago.macie...@intel.com wrote:
On sexta-feira, 29 de novembro de 2013 12:27:44, Sletta Gunnar wrote:
So, I'm asking that if you encounter issues with flickering, crashes, bad
rendering and similar, help
-
Gunnar
On 29. nov. 2013, at 19:02, Thiago Macieira thiago.macie...@intel.com
wrote:
On sexta-feira, 29 de novembro de 2013 12:27:44, Sletta Gunnar wrote:
So, I'm asking that if you encounter issues with flickering, crashes, bad
rendering and similar, help us track which things are
On Fri, Nov 29, 2013 at 7:01 PM, Thiago Macieira
thiago.macie...@intel.com wrote:
On sexta-feira, 29 de novembro de 2013 12:27:44, Sletta Gunnar wrote:
So, I'm asking that if you encounter issues with flickering, crashes, bad
rendering and similar, help us track which things are problematic by
Hi,
As many of you might already have noticed, OpenGL drivers are not always
working as well as would like. This has always been a problem, but since Qt
Creator 3.0 is using Qt Quick 2.0 and Qt Quick 2.0 is also being used in more
and more places, the problem is becoming more mainstream. We
As many of you might already have noticed, OpenGL drivers are not always
working as well as would like.
To what extent does this apply to different platforms and vendors? Is
Qt doing anything different from other GL apps on the same platform or
are they facing the same issues?
On 29 November
On Friday 29 November 2013 14:20:48 Robert Knight wrote:
As many of you might already have noticed, OpenGL drivers are not always
working as well as would like.
To what extent does this apply to different platforms and vendors? Is
Qt doing anything different from other GL apps on the same
On sexta-feira, 29 de novembro de 2013 12:27:44, Sletta Gunnar wrote:
So, I'm asking that if you encounter issues with flickering, crashes, bad
rendering and similar, help us track which things are problematic by filing
a bugreport on bugreports.qt-project.org and use the label driverissue in
27 matches
Mail list logo
