On terça-feira, 3 de dezembro de 2013 07:42:27, Knoll Lars wrote:
> I think people simply forgot about it. The message went out just before
> christmas last year, when everybody was just happy to have gotten 5.0 out.
> So let’s give people another few weeks to fix atomics for 5.3.
They can have a
On 03.12.13 03:02, "Thiago Macieira" wrote:
>On quarta-feira, 19 de dezembro de 2012 15:00:41, Thiago Macieira wrote:
>> I'd like to propose the following:
>> - Qt 5.1 deprecates the old atomic code and their platforms
>> - Qt 5.2 *removes* the code that doesn't get updated
>
>Looks like we for
Yes, very good point..
For windows it is important to know if we are on ANGLE or DesktopGL and on XCB
it is important to know if xcb was built with EGL or XGL.
cheers,
Gunnar
Fra: development-bounces+gunnar.sletta=digia@qt-project.org
[development-bo
Hi,
It was my mistake, I assumed that Qt Quick Controls are using the widgets
style plugins but it seems it was removed. I updated the article. Errare
humanum est!
So, Android style is available only for QWidget based apps and only if you are
using Ministro deploying system.
Cheers,
BogDan
On segunda-feira, 2 de dezembro de 2013 18:02:22, Thiago Macieira wrote:
> And the actual removal to dev:
>
> https://codereview.qt-project.org/73054
Which has enabled 11 commits between cleanups and improvements I had been
keeping back for a while, plus one more that I need to fix confl
On quarta-feira, 19 de dezembro de 2012 15:00:41, Thiago Macieira wrote:
> I'd like to propose the following:
> - Qt 5.1 deprecates the old atomic code and their platforms
> - Qt 5.2 *removes* the code that doesn't get updated
Looks like we forgot to announce the deprecation in Qt 5.1. I've just
Solved by adding the following to my .pro file:
QT += multimedia
QTPLUGIN += qavfcamera
On 2 December 2013 23:14, Ynon Perek wrote:
> Hi All,
>
> I tried to run the following QML on my iPhone 5, and got the error:
> defaultServiceProvider::requestService(): no service found for -
> "org.qt-
Hi All,
I tried to run the following QML on my iPhone 5, and got the error:
defaultServiceProvider::requestService(): no service found for -
"org.qt-project.qt.camera"
Camera error: "The camera service is missing”
Qt version is 5.2 RC1. The code works well on my laptop.
Any ideas ?
imp
On Mon, Dec 2, 2013 at 1:06 AM, Smith Martin wrote:
> For a QML type in a .qml file, qdoc reports an error if it sees a QML
> property it thinks should be in the public API for that QML type and there is
> no \qmlproperty comment immediately preceding that property in the .qml file.
>
> But for
On segunda-feira, 2 de dezembro de 2013 16:28:06, Ziller Eike wrote:
> On Dec 2, 2013, at 4:44 PM, Thiago Macieira
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
> >> y
> 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 wrote:
> On 2 December 2013 16:
On 2 December 2013 16:44, Thiago Macieira 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
On Dec 2, 2013, at 4:44 PM, Thiago Macieira 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 good, so I can re
Hi,
In BogDan's blog post about Qt for Android
(http://www.kdab.com/qt-on-android-episode-1/), in the first table he
mentions that native styling for Android will be available in Qt 5.2.
Using Qt 5.2 RC1, it doesn't seem like native styling is available. Is
this something still planned for Qt 5.2
On segunda-feira, 2 de dezembro de 2013 13:22:18, Koehne Kai wrote:
> Please make sure to include your exact graphics driver version (e.g. output
> of `glxinfo | grep string`) , and maybe check some of the things gunnar was
> writing recently:
>
> - Does upgrading driver or installing latest vendo
On Fri, Nov 29, 2013 at 09:50:31PM +0100, André Pönitz wrote:
> The scheme is fairly close to what Qt Creator's use of CI looks like
> (non-blocking, nag mails if things break, nothing stopping quick fixes),
> and it's a state that I am rather happy with.
>
i'm not.
(surprise surprise)
> Sure, thi
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
>> d
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 compon
> -Original Message-
> From: development-bounces+kai.koehne=digia@qt-project.org
> [mailto:development-bounces+kai.koehne=digia@qt-project.org] On
> Behalf Of Simon Lees
> Sent: Sunday, December 01, 2013 11:54 PM
> To: development@qt-project.org
> Subject: Re: [Development] Qt 5.2
On 11/29/2013 11:37 PM, Poenitz Andre wrote:
> Simon Lees [simon.l...@codanradio.com]
>> The version of QtCreator shipped with the package crashes my x everytime
>> i attempt to launch it. It was the Android Linux x86_64 package running
>> on openSUSE 12.3 with Enlightenment as the window manager
> 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 wro
Hi Thiago,
On 29/11/2013 17:58, Thiago Macieira wrote:
> On sexta-feira, 29 de novembro de 2013 14:48:23, Joseph Heenan wrote:
>> (I'm not a member of the QT project so I'm not sure if this is something
>> that should be added to the wiki page, nor if it would be correct
>> protocol for me to add
On Sunday 01 December 2013 13:53:50 Chris Colbert wrote:
> I recently had a change-set merged which fixed the WA_StaticContents flag
> on Windows. However, when I update my git repo according to the advice on
> the website:
>
>
>1. git pull
>2. git submodule sync
>3. git submodule upd
On Mon, Dec 2, 2013 at 10:06 AM, Smith Martin wrote:
> For a QML type in a .qml file, qdoc reports an error if it sees a QML
> property it thinks should be in the public API for that QML type and there is
> no \qmlproperty comment immediately preceding that property in the .qml file.
>
> But for
On Nov 30, 2013, at 10:29 PM, Mark Gaiser wrote:
> On Fri, Nov 29, 2013 at 7:01 PM, Thiago Macieira
> 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
On 2.12.2013 9.59, "Yves Bailly" wrote:
>Greetings everyone,
>
>Le 28/11/2013 14:36, Heikkinen Jani a écrit :
>> We have finally Qt 5.2 RC1 candidate packages available in
>>
>>http://download.qt-project.org/snapshots/qt/5.2/5.2.0-rc1/2013-11-28_179/
>> . Mirroring is ongoing so
>> it is possib
For a QML type in a .qml file, qdoc reports an error if it sees a QML property
it thinks should be in the public API for that QML type and there is no
\qmlproperty comment immediately preceding that property in the .qml file.
But for a QML type that is represented by a C++ class, qdoc doesn't kn
Greetings everyone,
Le 28/11/2013 14:36, Heikkinen Jani a écrit :
> We have finally Qt 5.2 RC1 candidate packages available in
> http://download.qt-project.org/snapshots/qt/5.2/5.2.0-rc1/2013-11-28_179/ .
> Mirroring is ongoing so
> it is possible that all packages aren’t visible yet but will be
28 matches
Mail list logo
