Re: [Interest] Custom QPushButton

2013-11-22 Thread Graham Labdon
Thanks for that - I will give it a try

-Original Message-
From: interest-bounces+graham.labdon=avalonsciences@qt-project.org 
[mailto:interest-bounces+graham.labdon=avalonsciences@qt-project.org] On 
Behalf Of Rayner Pupo
Sent: 22 November 2013 03:00
To: interest@qt-project.org
Subject: [Interest] Custom QPushButton

You can do whatever you want by subclassing QPushButton and reimplementing 
paintEvent function. 
using QStyleOptionButton you can draw the button exactly like a normal one but 
looking allways like normal state, just set the propper button feature for the 
styleOption 

III Escuela Internacional de Invierno en la UCI del 17 al 28 de febrero del 
2014. Ver www.uci.cu ___
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] Glyph fallback

2013-11-22 Thread Ender Erel
Hi All,

I think my approach was wrong the whole time, so let me try again.

I am working on QtEmbedded 4.1.4. I have three fonts: FontA contains Latin, 
FontB contains Korean, FontC contains Chinese characters and each font is from 
a different family. I also have three labels in my app (LabelA, LabelB, 
LabelC), each containing text in each language respectively. What i want to 
achieve is: Render all labels successfully, without setting fonts per language 
explicitly on the labels.

We are using the legacy fontdir file approach mentioned in the following page:
http://qt-project.org/doc/qt-4.8/qt-embedded-fonts.html

When i check the QFontDatabase, all three fonts are found.

Now, here is my problem: When i use QApplication::setFont(FontA), only the 
text in LabelA is visible (same for FontB-LabelB and FontC-LabelC). I use 
QFont::AnyStyle  QFont::PreferDefault as style hintstrategy. So I thought Qt 
would take the characters from the other fonts, but it doesn't.

I was told that fontconfig was the way to go, but as mentioned on this page, 
fontconfig is not supported on QtEmbeeded, therefore i gave up on that.
http://qt-project.org/doc/qt-5.0/qtdoc/qt-embedded-fonts.html

Then i saw the following page:
http://stackoverflow.com/questions/14125081/how-to-properly-output-multilingual-text-in-qt-embedded
...and tried the QSWS_NO_SHARE_FONTS=1 fix, but that didn't solve my problem 
either. The poster says he's got multiple fonts from the same family, and he 
successfully uses them at the same time without explicitly setting them 
per-widget, so why can't i do it? The only difference i can think of is the 
family issue, (his fonts are the same family, mine aren't).

I can't figure out why Qt can't render text in different languages without 
explicitly setting the font per widget, like it does in the CharacterMap 
example with Font Merging checked.

Any help is much appreciated.

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


Re: [Interest] [SOLVED] QImage::save forces client to open file before call

2013-11-22 Thread alexander golks
Am Thu, 21 Nov 2013 07:52:08 -0800
schrieb Thiago Macieira thiago.macie...@intel.com:

 If you think the behaviour is wrong, describe it and ask that it be fixed in 
 a 
 bug report.

you wrote, i debugged again, and found just our not-qt-tif plugin behaves not 
like all other plugins... i should have looked better at the code.

nevertheless it worked before and the error looked strange to me, and the 
reason for the code change interested me.

thx for the hint, and sorry for the noise.

-- 
/*
 *  /* James M doesn't say fuck enough. *\/
 *  linux-2.4.3/net/core/netfilter.c
 */


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


Re: [Interest] OpenGL ES2.0 on target board

2013-11-22 Thread Koehne Kai


 -Original Message-
 From: interest-bounces+kai.koehne=digia@qt-project.org
 [mailto:interest-bounces+kai.koehne=digia@qt-project.org] On Behalf Of
 Ramesh Nelakuditi
 Sent: Friday, November 22, 2013 7:32 AM
 To: Interest@qt-project.org
 Subject: [Interest] OpenGL ES2.0 on target board
 
 Hi,
 
 We are developing Qt widgets application using Qt 5.1.1 SDK.
 
 We plan to use CUPID i.MX35 board (http://www.garz-fricke.com/cupid-57-
 boxed_en.html http://www.garz-fricke.com/cupid-57-boxed_en.html )
 which has only Linux frame buffer support.
 
 I understand for classes QQuickItem or QSG* or QML, we need to have
 support for OpenGL ES2.0 on target board.
 
 Incase we use QtGraphics view framework, does it needs to support OPEN GL
 ES2.0 on target board ?

QGraphicsView is part of QtWidgets, and doesn't have an OpenGL dependency.

Regards

Kai
 
 Thanks,
 Ramesh.
 
 
 
 
 
 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.

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


[Interest] Qt Quick on desktop applications

2013-11-22 Thread Graham Labdon
Hi
Is it viable to develop a complex desktop application using QML for the user 
interface?
Regards

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


[Interest] static qt without zlib

2013-11-22 Thread Tim Blechmann
hi all,

i'm trying to compile qt as static library with msvc2012. is it possible
to do this without building zlib? my application provides its own
version of zlib, so i'm currently having duplicate symbols from my own
static zlib and Qt5Core.lib

any idea?

thanks in advance,
tim



signature.asc
Description: OpenPGP digital signature
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest


Re: [Interest] Windows segfault, but not on Linux

2013-11-22 Thread Konrad Rosenbaum
Ok, let me qualify my statement: never assume var++ is atomic unless it is an 
explicit atomic int or protected by a mutex!

In this specific case neither was an option: I would have had to rewrite some 
important chunks of a 3rd-party lib that were already tricky to debug. So I 
wrote a workaround making sure the affected data structures do not cross 
threads.

The nice thing about killing bugs with tanks is that it is so inefficient and 
damaging that it is likely to lead to more (paid) work... ;-)

Funnily enough the same is true for fixing things with sticky tape... ;-)



Konrad

On Thursday, Thursday 21 November 2013 at 19:15, Etienne Sandré-Chardonnal 
wrote:
 Hey, that's using a tank for killing a bug. Why not std::atomicint or
 QAtomicInt ? In heavy cases (such as mine...) that's a huge performance
 issue and code is also lighter.
 
 2013/11/21 Konrad Rosenbaum kon...@silmor.de
 
  Hint 2: never assume something as innocuous as var++ is an atomic
  operation unless it is protected by a Mutex! My most recent hard-to-fix
  on-Windows-only crash was a race between refcnt++ and refcnt-- in a
  library that I didn't even write myself (libtcl).


signature.asc
Description: This is a digitally signed message part.
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest


Re: [Interest] Qt Quick on desktop applications

2013-11-22 Thread Tomasz Siekierda
On 22 November 2013 11:22, Graham Labdon
graham.lab...@avalonsciences.com wrote:

 Hi
 Is it viable to develop a complex desktop application using QML for the user 
 interface?
 Regards


Yes. But better make some test apps before you commit to that. QML is
very easy and powerful, but needs a bit getting used to (it's very
different from C++, that all).
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest


Re: [Interest] Qt Quick on desktop applications

2013-11-22 Thread Frédéric Meurou
Hi Graham,

IMHO,  it is viable since :
- you'll get more and more touch screens
- people are getting used to touch interfaces
- Quick Controls allows you to mimick widgets
- You get GL acceleration on QML
- it is easy to create custom components.

From my recent experience, I don't think i'll use widgets anymore.

Regards,

Frederic



2013/11/22 Graham Labdon graham.lab...@avalonsciences.com

  Hi
 Is it viable to develop a complex desktop application using QML for the
 user interface?
 Regards


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




-- 
*Frédéric MEUROU*
*Directeur Technique*
*Wapp**6*
*Mob*  *+33 6 07 34 62 13*
*Fixe  *+33 1 79 84 17 57
*Email*   *fmeu...@wapp6.com* fmeu...@wapp6.com* ohus...@wapp6.com*
*Adresse* 191 avenue Aristide Briand, 94230 Cachan

*www.wapp6.com http://www.wapp6.com/*

*Avant d’imprimer cet email, pensez à l’environnement.*

*Ce message et toutes les pièces jointes (ci-après le message) sont
établis à l'intention exclusive de ses destinataires et sont confidentiels.
Si vous recevez ce message par erreur, merci de le détruire et d'en avertir
immédiatement l'expéditeur. Toute utilisation de ce message non conforme à
sa destination, toute diffusion ou toute publication, totale ou partielle,
est interdite, sauf autorisation expresse. L'internet ne permettant pas
d'assurer l'intégrité de ce message, WAPP6  (et ses filiales) décline(nt)
toute responsabilité au titre de ce message, dans l'hypothèse ou il aurait
été modifié, altéré ou falsifié.*
*WAPP6  vous remercie de votre attention.*
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest


Re: [Interest] Qt Quick on desktop applications

2013-11-22 Thread Graham Labdon
Sounds like it's worth looking at
Would it be difficult to convert an existing ui to Qml?

From: Frédéric Meurou [mailto:fmeu...@wapp6.com]
Sent: 22 November 2013 10:38
To: Graham Labdon
Cc: Interest@qt-project.org
Subject: Re: [Interest] Qt Quick on desktop applications

Hi Graham,
IMHO,  it is viable since :
- you'll get more and more touch screens
- people are getting used to touch interfaces
- Quick Controls allows you to mimick widgets
- You get GL acceleration on QML
- it is easy to create custom components.
From my recent experience, I don't think i'll use widgets anymore.
Regards,
Frederic


2013/11/22 Graham Labdon 
graham.lab...@avalonsciences.commailto:graham.lab...@avalonsciences.com
Hi
Is it viable to develop a complex desktop application using QML for the user 
interface?
Regards


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



--
Frédéric MEUROU
Directeur Technique
Wapp6
Mob  +33 6 07 34 62 13
Fixe  +33 1 79 84 17 57
Email   fmeu...@wapp6.commailto:fmeu...@wapp6.com
Adresse 191 avenue Aristide Briand, 94230 Cachan

www.wapp6.comhttp://www.wapp6.com/

Avant d'imprimer cet email, pensez à l'environnement.

Ce message et toutes les pièces jointes (ci-après le message) sont établis à 
l'intention exclusive de ses destinataires et sont confidentiels. Si vous 
recevez ce message par erreur, merci de le détruire et d'en avertir 
immédiatement l'expéditeur. Toute utilisation de ce message non conforme à sa 
destination, toute diffusion ou toute publication, totale ou partielle, est 
interdite, sauf autorisation expresse. L'internet ne permettant pas d'assurer 
l'intégrité de ce message, WAPP6  (et ses filiales) décline(nt) toute 
responsabilité au titre de ce message, dans l'hypothèse ou il aurait été 
modifié, altéré ou falsifié.
WAPP6  vous remercie de votre attention.
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest


Re: [Interest] Qt Quick on desktop applications

2013-11-22 Thread Frédéric Meurou
I guess with Quick Controls and layout elements it might be easy.

My approach would be to rethink the UI considering new possibilities
offered by QML, which is much more flexible when it comes to UI design.



Le 22 novembre 2013 10:47, Graham Labdon
graham.lab...@avalonsciences.coma écrit :

  Sounds like it’s worth looking at

 Would it be difficult to convert an existing ui to Qml?



 *From:* Frédéric Meurou [mailto:fmeu...@wapp6.com]
 *Sent:* 22 November 2013 10:38
 *To:* Graham Labdon
 *Cc:* Interest@qt-project.org
 *Subject:* Re: [Interest] Qt Quick on desktop applications



 Hi Graham,

 IMHO,  it is viable since :
 - you'll get more and more touch screens

 - people are getting used to touch interfaces

 - Quick Controls allows you to mimick widgets

 - You get GL acceleration on QML

 - it is easy to create custom components.

 From my recent experience, I don't think i'll use widgets anymore.

 Regards,

 Frederic





 2013/11/22 Graham Labdon graham.lab...@avalonsciences.com

 Hi

 Is it viable to develop a complex desktop application using QML for the
 user interface?

 Regards




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




 --

 *Frédéric MEUROU*
 *Directeur Technique*
 *Wapp**6*

 *Mob*  *+33 6 07 34 62 13 %2B33%206%2007%2034%2062%2013*

 *Fixe  *+33 1 79 84 17 57
 *Email*   fmeu...@wapp6.com
 *Adresse* 191 avenue Aristide Briand, 94230 Cachan

 *www.wapp6.com http://www.wapp6.com/*


 *Avant d’imprimer cet email, pensez à l’environnement.*

 *Ce message et toutes les pièces jointes (ci-après le message) sont
 établis à l'intention exclusive de ses destinataires et sont confidentiels.
 Si vous recevez ce message par erreur, merci de le détruire et d'en avertir
 immédiatement l'expéditeur. Toute utilisation de ce message non conforme à
 sa destination, toute diffusion ou toute publication, totale ou partielle,
 est interdite, sauf autorisation expresse. L'internet ne permettant pas
 d'assurer l'intégrité de ce message, WAPP6  (et ses filiales) décline(nt)
 toute responsabilité au titre de ce message, dans l'hypothèse ou il aurait
 été modifié, altéré ou falsifié.*
 *WAPP6  vous remercie de votre attention.*




-- 
*Frédéric MEUROU*
*Directeur Technique*
*Wapp**6*
*Mob*  *+33 6 07 34 62 13*
*Fixe  *+33 1 79 84 17 57
*Email*   *fmeu...@wapp6.com* fmeu...@wapp6.com* ohus...@wapp6.com*
*Adresse* 191 avenue Aristide Briand, 94230 Cachan

*www.wapp6.com http://www.wapp6.com/*

*Avant d’imprimer cet email, pensez à l’environnement.*

*Ce message et toutes les pièces jointes (ci-après le message) sont
établis à l'intention exclusive de ses destinataires et sont confidentiels.
Si vous recevez ce message par erreur, merci de le détruire et d'en avertir
immédiatement l'expéditeur. Toute utilisation de ce message non conforme à
sa destination, toute diffusion ou toute publication, totale ou partielle,
est interdite, sauf autorisation expresse. L'internet ne permettant pas
d'assurer l'intégrité de ce message, WAPP6  (et ses filiales) décline(nt)
toute responsabilité au titre de ce message, dans l'hypothèse ou il aurait
été modifié, altéré ou falsifié.*
*WAPP6  vous remercie de votre attention.*
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest


Re: [Interest] Qt Quick on desktop applications

2013-11-22 Thread Graham Labdon
My application has some rather complicated graphical aspects such as displaying 
large data sets as a plotted graph.
Would this be possible in qml?

From: Frédéric Meurou [mailto:fmeu...@wapp6.com]
Sent: 22 November 2013 10:51
To: Graham Labdon
Cc: Interest@qt-project.org
Subject: Re: [Interest] Qt Quick on desktop applications

I guess with Quick Controls and layout elements it might be easy.

My approach would be to rethink the UI considering new possibilities offered by 
QML, which is much more flexible when it comes to UI design.

Le 22 novembre 2013 10:47, Graham Labdon 
graham.lab...@avalonsciences.commailto:graham.lab...@avalonsciences.com a 
écrit :
Sounds like it's worth looking at
Would it be difficult to convert an existing ui to Qml?

From: Frédéric Meurou [mailto:fmeu...@wapp6.commailto:fmeu...@wapp6.com]
Sent: 22 November 2013 10:38
To: Graham Labdon
Cc: Interest@qt-project.orgmailto:Interest@qt-project.org
Subject: Re: [Interest] Qt Quick on desktop applications

Hi Graham,
IMHO,  it is viable since :
- you'll get more and more touch screens
- people are getting used to touch interfaces
- Quick Controls allows you to mimick widgets
- You get GL acceleration on QML
- it is easy to create custom components.
From my recent experience, I don't think i'll use widgets anymore.
Regards,
Frederic


2013/11/22 Graham Labdon 
graham.lab...@avalonsciences.commailto:graham.lab...@avalonsciences.com
Hi
Is it viable to develop a complex desktop application using QML for the user 
interface?
Regards


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



--
Frédéric MEUROU
Directeur Technique
Wapp6
Mob  +33 6 07 34 62 13tel:%2B33%206%2007%2034%2062%2013
Fixe  +33 1 79 84 17 57tel:%2B33%201%2079%2084%2017%2057
Email   fmeu...@wapp6.commailto:fmeu...@wapp6.com
Adresse 191 avenue Aristide Briand, 94230 Cachan

www.wapp6.comhttp://www.wapp6.com/

Avant d'imprimer cet email, pensez à l'environnement.

Ce message et toutes les pièces jointes (ci-après le message) sont établis à 
l'intention exclusive de ses destinataires et sont confidentiels. Si vous 
recevez ce message par erreur, merci de le détruire et d'en avertir 
immédiatement l'expéditeur. Toute utilisation de ce message non conforme à sa 
destination, toute diffusion ou toute publication, totale ou partielle, est 
interdite, sauf autorisation expresse. L'internet ne permettant pas d'assurer 
l'intégrité de ce message, WAPP6  (et ses filiales) décline(nt) toute 
responsabilité au titre de ce message, dans l'hypothèse ou il aurait été 
modifié, altéré ou falsifié.
WAPP6  vous remercie de votre attention.



--
Frédéric MEUROU
Directeur Technique
Wapp6
Mob  +33 6 07 34 62 13
Fixe  +33 1 79 84 17 57
Email   fmeu...@wapp6.commailto:fmeu...@wapp6.com
Adresse 191 avenue Aristide Briand, 94230 Cachan

www.wapp6.comhttp://www.wapp6.com/

Avant d'imprimer cet email, pensez à l'environnement.

Ce message et toutes les pièces jointes (ci-après le message) sont établis à 
l'intention exclusive de ses destinataires et sont confidentiels. Si vous 
recevez ce message par erreur, merci de le détruire et d'en avertir 
immédiatement l'expéditeur. Toute utilisation de ce message non conforme à sa 
destination, toute diffusion ou toute publication, totale ou partielle, est 
interdite, sauf autorisation expresse. L'internet ne permettant pas d'assurer 
l'intégrité de ce message, WAPP6  (et ses filiales) décline(nt) toute 
responsabilité au titre de ce message, dans l'hypothèse ou il aurait été 
modifié, altéré ou falsifié.
WAPP6  vous remercie de votre attention.
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest


Re: [Interest] Qt Quick on desktop applications

2013-11-22 Thread Frédéric Meurou
AFAIK, you have to possibilities :
- proprietary Qt from Digia with Qt.Charts
- build your own chart renderer with a QQuickPaintedItem (i created torus
graphs quite easily, but it's only a one dimension graph).

but you won't get native charts from the open source version.



Le 22 novembre 2013 10:55, Graham Labdon
graham.lab...@avalonsciences.coma écrit :

  My application has some rather complicated graphical aspects such as
 displaying large data sets as a plotted graph.

 Would this be possible in qml?



 *From:* Frédéric Meurou [mailto:fmeu...@wapp6.com]
 *Sent:* 22 November 2013 10:51
 *To:* Graham Labdon
 *Cc:* Interest@qt-project.org
 *Subject:* Re: [Interest] Qt Quick on desktop applications



 I guess with Quick Controls and layout elements it might be easy.



 My approach would be to rethink the UI considering new possibilities
 offered by QML, which is much more flexible when it comes to UI design.



 Le 22 novembre 2013 10:47, Graham Labdon graham.lab...@avalonsciences.com
 a écrit :

 Sounds like it’s worth looking at

 Would it be difficult to convert an existing ui to Qml?



 *From:* Frédéric Meurou [mailto:fmeu...@wapp6.com]
 *Sent:* 22 November 2013 10:38
 *To:* Graham Labdon
 *Cc:* Interest@qt-project.org
 *Subject:* Re: [Interest] Qt Quick on desktop applications



 Hi Graham,

 IMHO,  it is viable since :
 - you'll get more and more touch screens

 - people are getting used to touch interfaces

 - Quick Controls allows you to mimick widgets

 - You get GL acceleration on QML

 - it is easy to create custom components.

 From my recent experience, I don't think i'll use widgets anymore.

 Regards,

 Frederic





 2013/11/22 Graham Labdon graham.lab...@avalonsciences.com

 Hi

 Is it viable to develop a complex desktop application using QML for the
 user interface?

 Regards




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




 --

 *Frédéric MEUROU*
 *Directeur Technique*
 *Wapp**6*

 *Mob*  *+33 6 07 34 62 13 %2B33%206%2007%2034%2062%2013*

 *Fixe  *+33 1 79 84 17 57
 *Email*   fmeu...@wapp6.com
 *Adresse* 191 avenue Aristide Briand, 94230 Cachan

 *www.wapp6.com http://www.wapp6.com/*


 *Avant d’imprimer cet email, pensez à l’environnement.*

 *Ce message et toutes les pièces jointes (ci-après le message) sont
 établis à l'intention exclusive de ses destinataires et sont confidentiels.
 Si vous recevez ce message par erreur, merci de le détruire et d'en avertir
 immédiatement l'expéditeur. Toute utilisation de ce message non conforme à
 sa destination, toute diffusion ou toute publication, totale ou partielle,
 est interdite, sauf autorisation expresse. L'internet ne permettant pas
 d'assurer l'intégrité de ce message, WAPP6  (et ses filiales) décline(nt)
 toute responsabilité au titre de ce message, dans l'hypothèse ou il aurait
 été modifié, altéré ou falsifié.*
 *WAPP6  vous remercie de votre attention.*




 --

 *Frédéric MEUROU*
 *Directeur Technique*
 *Wapp**6*

 *Mob*  *+33 6 07 34 62 13 %2B33%206%2007%2034%2062%2013*

 *Fixe  *+33 1 79 84 17 57
 *Email*   fmeu...@wapp6.com
 *Adresse* 191 avenue Aristide Briand, 94230 Cachan

 *www.wapp6.com http://www.wapp6.com/*


 *Avant d’imprimer cet email, pensez à l’environnement.*

 *Ce message et toutes les pièces jointes (ci-après le message) sont
 établis à l'intention exclusive de ses destinataires et sont confidentiels.
 Si vous recevez ce message par erreur, merci de le détruire et d'en avertir
 immédiatement l'expéditeur. Toute utilisation de ce message non conforme à
 sa destination, toute diffusion ou toute publication, totale ou partielle,
 est interdite, sauf autorisation expresse. L'internet ne permettant pas
 d'assurer l'intégrité de ce message, WAPP6  (et ses filiales) décline(nt)
 toute responsabilité au titre de ce message, dans l'hypothèse ou il aurait
 été modifié, altéré ou falsifié.*
 *WAPP6  vous remercie de votre attention.*




-- 
*Frédéric MEUROU*
*Directeur Technique*
*Wapp**6*
*Mob*  *+33 6 07 34 62 13*
*Fixe  *+33 1 79 84 17 57
*Email*   *fmeu...@wapp6.com* fmeu...@wapp6.com* ohus...@wapp6.com*
*Adresse* 191 avenue Aristide Briand, 94230 Cachan

*www.wapp6.com http://www.wapp6.com/*

*Avant d’imprimer cet email, pensez à l’environnement.*

*Ce message et toutes les pièces jointes (ci-après le message) sont
établis à l'intention exclusive de ses destinataires et sont confidentiels.
Si vous recevez ce message par erreur, merci de le détruire et d'en avertir
immédiatement l'expéditeur. Toute utilisation de ce message non conforme à
sa destination, toute diffusion ou toute publication, totale ou partielle,
est interdite, sauf autorisation expresse. L'internet ne permettant pas
d'assurer l'intégrité de ce message, WAPP6  (et ses filiales) décline(nt)
toute responsabilité au titre de ce message, dans l'hypothèse ou il aurait
été modifié, 

Re: [Interest] Qt Quick on desktop applications

2013-11-22 Thread Philipp Kursawe
No. I tried and it lacking basic UI features of the desktop like proper
keyboard handling and a proper combos, treeview.
Also the weird domain language which is a mix of JavaScript and json does
not help. Worst if all, it's difficult to debug.
--
From: Graham Labdon
Sent: 22.11.2013 11:22
To: Interest@qt-project.org
Subject: [Interest] Qt Quick on desktop applications

Hi
Is it viable to develop a complex desktop application using QML for the
user interface?
Regards
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest


Re: [Interest] static qt without zlib

2013-11-22 Thread Konrad Rosenbaum
Hi,

On Friday, Friday 22 November 2013 at 11:28, Tim Blechmann wrote:
 i'm trying to compile qt as static library with msvc2012. is it possible
 to do this without building zlib? my application provides its own
 version of zlib, so i'm currently having duplicate symbols from my own
 static zlib and Qt5Core.lib

Zlib is pretty basic to some Qt tools, e.g. Qt Resources (*.qrc) are 
compressed when compiled.

You might try to use a system zlib, i.e. provide your own copy of zlib as 
the one Qt links to and then use the one linked inside Qt.

Why are you using static linking anyway?


Konrad


signature.asc
Description: This is a digitally signed message part.
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest


[Interest] Keyboard navigation issues in Quick2

2013-11-22 Thread Ola Røer Thorsen
Hi all,

here is a case that I find rather limiting and time-consuming. It has to do
with focus scopes and keyboard navigation. I'm looking for a best way to
deal with the following situation:

- I have a ColumnLayout of button-like items, like a popup-menu.
- The first item has focus set to true.
- KeyNavigation.down is used to walk between these to move focus.
- The Items' enabled-value can be set to false if this item is
unavailable for some reason. In this case KeyNavigation works fine and
jumps past the element and on to the next (good).

However if you try to activate focus on the first item (using KeyNavigation
from some other item), and it is disabled, you get no focus at all, and
keyboard navigation is stuck.

I would expect that focus would move on to the next item in the focus
scope, if the item with active focus was disabled.

Also if you disable the item that has focus, focus does not move to the
next item. So you're stuck again.

Why would I disable one of the items? Well if this is a menu, it could be
that one of the menu actions are unavailable for some reason.

Isn't this a bug? It can be worked around with ugly javascript code, but
the fixes are not scalable and you will need calling forceActiveFocus on
items instead.

KeyNavigation seems to be way to create a focus order chain similar to
what you could do with widgets. Or am I wrong?

Below is an example snippet that demonstrate these two issues (tested with
Qt5.2RC1). It has two columns that you can jump between using the cursor
keys. Press the spacebar to disable the upper left box, and see what
happens if focus is on the right, or focus is on left box 1.

Best regards,
Ola


import QtQuick 2.1
import QtQuick.Layouts 1.0

Rectangle {
width: 800
height: 480

Keys.onSpacePressed: {
box1.enabled = !box1.enabled;
}

Text {
anchors.centerIn: parent
text: Use cursor keys to move focus around.\nPush spacebar to
toggle box1 enabled.\n\nNote that it is not possible to go from the right
boxes to\nthe left if box1 is disabled (gray).\nYou'd expect that box2
would get focus if box1 is disabled.\nIt is also possible to get stuck if
box1 is disabled while it has active focus.\n
}

ColumnLayout {
anchors.left: parent.left
anchors.top: parent.top
anchors.bottom: parent.bottom
width: 200

Rectangle {
focus: true
id: box1
color: enabled ? (activeFocus ? green : orange) : gray
width: 180
height: 30
Text {
anchors.fill: parent
text: box1
}
KeyNavigation.down: box2
KeyNavigation.right: rbox1
}

Rectangle {
focus: true
id: box2
color: enabled ? (activeFocus ? green : orange) : gray
width: 180
height: 30
Text {
anchors.fill: parent
text: box2
}
KeyNavigation.down: box3
KeyNavigation.right: rbox1
}

Rectangle {
focus: true
id: box3
color: enabled ? (activeFocus ? green : orange) : gray
width: 180
height: 30
Text {
anchors.fill: parent
text: box3
}
KeyNavigation.down: box4
KeyNavigation.right: rbox1
}

Rectangle {
focus: true
id: box4
color: enabled ? (activeFocus ? green : orange) : gray
width: 180
height: 30
Text {
anchors.fill: parent
text: box4
}
KeyNavigation.down: box1
KeyNavigation.right: rbox1
}
}
ColumnLayout {
anchors.right: parent.right
anchors.top: parent.top
anchors.bottom: parent.bottom
width: 200

Rectangle {
focus: true
id: rbox1
color: enabled ? (activeFocus ? green : orange) : gray
width: 180
height: 30
Text {
anchors.fill: parent
text: rightbox1
}
KeyNavigation.down: rbox2
KeyNavigation.left: box1
}
Rectangle {
focus: true
id: rbox2
color: enabled ? (activeFocus ? green : orange) : gray
width: 180
height: 30
Text {
anchors.fill: parent
text: rightbox2
}
KeyNavigation.down: rbox1
KeyNavigation.left: box1
}
}

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


Re: [Interest] Keyboard navigation issues in Quick2

2013-11-22 Thread Liang Qi
Hi, Ola,

Just got notification about your question from others, and subscribed this
mailing list.
http://lists.qt-project.org/pipermail/interest/2013-November/009878.html

Your question is valid here in some way. I think you could create a bug
report in jira.

There is no focus chain concept when Qt Quick 2 was ready at the beginning.
We tried to support sth like that in this feature,
QQuickItem::activeFocusOnTab:
http://qt-project.org/doc/qt-5.1/qtquick/qml-qtquick2-item.html#activeFocusOnTab-prop

And it doesn't cover the case like your code, KeyNavigation will not work
when the Item is disabled itself. You need to maintain the focus chain
yourself in current code. Maybe we could support it in Qt side in the
future.

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


Re: [Interest] static qt without zlib

2013-11-22 Thread Tim Blechmann
hi konrad,

 i'm trying to compile qt as static library with msvc2012. is it possible
 to do this without building zlib? my application provides its own
 version of zlib, so i'm currently having duplicate symbols from my own
 static zlib and Qt5Core.lib
 
 Zlib is pretty basic to some Qt tools, e.g. Qt Resources (*.qrc) are 
 compressed when compiled.

well it is not that i want to completely remove zlib, but i currently
have too many of them ;)


 You might try to use a system zlib, i.e. provide your own copy of zlib as 
 the one Qt links to and then use the one linked inside Qt.

i've already tried to compile with -system-zlib, but Qt5Core.lib still
contains zlib symbols.
or do i need to/am i able to explicitly specify my zlib when compiling qt?


 Why are you using static linking anyway?

i'm using qt from a plugin context. static linking will avoid some
problems which could occur when linking dynamically.

thnx,
tim




signature.asc
Description: OpenPGP digital signature
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest


Re: [Interest] Tearing in Quick2 flickable-based items with clipping enabled

2013-11-22 Thread Ola Røer Thorsen
Thanks for the feedback both of you!

VStevenP, yes I've looked at the TI wiki regarding failure modes and
whatnot, and tried setting the paramBufferSize and such. Doesn't seem have
any effect on the tearing. I think they might have some race condition in
the gpu driver or something,

My application is running at 800x480. I knew the SGX wasn't very powerful
before starting coding so I didn't expect too much. Therefore I've actually
been rather happy with the general results. I've done things like
- Make sure to set the background color on the QuickView and NOT fill the
whole screen with a background rectangle the way most example snippets do
- Avoid animating movement of large Items (looks jerky anyway), I just fade
opacity in/out.
- At least in 5.1.1 opacity = 0 is slower than visible = false so I make
sure to set visible = false as often as possible (documentation examples
often say it's enough to do opacity=0)
- Try to avoid clip = true, and never use smooth = true
- Keep javascript logic to an absolute minimum, move as much as possible to
c++ (the arm core isn't the quickest one either).
- Use dynamic creation of larger gui modules on demand, to limit the amount
of active bindings on things that aren't on screen. The annoying bit here
is the waiting pause when the new QML items are compiled on the fly. You
don't notice that on the Desktop, but you sure do on ARM.

Compared with my previous application based on Qt4's widgets that I now
have replaced, the new one uses just a third of the cpu load, with much
smoother and more complex things happening on the screen.

I hope to try 5.2 as soon as possible.

Cheers,
Ola





2013/11/20 VStevenP vstevenpa...@yahoo.com

 Hi Gunnar -

 Thanks for these performance improvement ideas.

 I write QtQuick2 apps.  I'll see if I can use requestedFormat().  (I know
 how to write widgets in C++ and make them available in QML.)

 I rechecked my emails, and it was a Digia rep who made the comment about
 800x600:

 The SGX chip on the BeagleBoard is not really capable of running any
 advanced graphics at a high display resolution, which is why we have set it
 to 800x600 by default. This is the highest resolution with which we are
 comfortable performance wise.

 That said, you are correct - it's not Qt's fault for SGX GPU shortcomings.

 Yes, DM3730 on BB-xM supports CPU frequency scaling.  I don't think I'm
 using frequency scaling in my current configuration, because I am using
 Angstrom 2011.03 from Narcissus Image builder.  I'll get a new package from
 Narcissus which contains cpufrequtils and investigate.  I really hope I can
 document that CPU usage of simple custom QtQuick2-based widgets is
 reasonable on DM3730/BB-xM.

 - VStevenP

 
 On Wed, 11/20/13, Sletta Gunnar gunnar.sle...@digia.com wrote:

  Subject: SV: [Interest] Tearing in Quick2 flickable-based items with
 clipping enabled
  To: vstevenpa...@yahoo.com vstevenpa...@yahoo.com, Ola Røer
 Thorsen o...@silentwings.no, interest@qt-project.org 
 interest@qt-project.org
  Date: Wednesday, November 20, 2013, 1:58 AM

   I find frame rate issues when
  using:
  
   * opacity that is not equal to zero or one
   * rounded rectangles a.k.a Rectangles with specified
  radius property
   * clip property (sometimes)

  The SGX does not do GL_BLEND very well. In fact it does it
  quite badly, so opacity other than 0 an 1 should be avoided
  at all costs on this hardware. Qt Quick will potentially
  make this worse when antialiasing is used on items as the
  antialiasing is implemented by default by using vertex
  opacity and the entire primitive becomes blended, regardless
  of its shape.

  5.2 makes it possible to prefer multisample antialiasing
  over vertex antialiasing by adding
  QSurfaceFormat::setSamples() to
  QQuickWindow::requestedFormat().

  QSurfaceFormat format = window.requestedFormat();
  format.setSamples(4);
  window.setFormat(format);

  This will cause both images and rectangles to use MSAA for
  antialiasing which means that the primitives themselves are
  fully opaque. With the new renderer this is even better as
  opaque primitives can be freely batched with very little
  overhead.

  The same can be acheived in Qt 5.1 by using a customcontext
  from
 https://github.com/qtproject/playground-scenegraph/tree/master/customcontext
  and configuring it with

qmake -config msaa

  That leaves image art. It generally has semi transparent
  areas and opaque areas and for hardware that doesn't do
  blending one ideally wants to split the image into its
  opaque and translucent parts. I started playing around with
  this in the spring here:
 https://github.com/qtproject/playground-scenegraph/tree/master/shapes
  It is working but not product quality at this point, but it
  gives an idea about what can be done.

   The problem is worse especially at higher resolution
  displays
   such as 1280x800.  Evidently, TI recommends to only
  drive a
   somewhat 

Re: [Interest] Keyboard navigation issues in Quick2

2013-11-22 Thread Ola Røer Thorsen
Hi Liang,

thanks for the reply! I will create a bug report right away.

Best regards,
Ola




2013/11/22 Liang Qi cavendish...@gmail.com

 Hi, Ola,

 Just got notification about your question from others, and subscribed this
 mailing list.
 http://lists.qt-project.org/pipermail/interest/2013-November/009878.html

 Your question is valid here in some way. I think you could create a bug
 report in jira.

 There is no focus chain concept when Qt Quick 2 was ready at the
 beginning. We tried to support sth like that in this feature,
 QQuickItem::activeFocusOnTab:

 http://qt-project.org/doc/qt-5.1/qtquick/qml-qtquick2-item.html#activeFocusOnTab-prop

 And it doesn't cover the case like your code, KeyNavigation will not work
 when the Item is disabled itself. You need to maintain the focus chain
 yourself in current code. Maybe we could support it in Qt side in the
 future.

 Regards,
 Liang

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


Re: [Interest] Keyboard navigation issues in Quick2

2013-11-22 Thread Ola Røer Thorsen
And here it is: https://bugreports.qt-project.org/browse/QTBUG-35051



2013/11/22 Ola Røer Thorsen o...@silentwings.no

 Hi Liang,

 thanks for the reply! I will create a bug report right away.

 Best regards,
 Ola




 2013/11/22 Liang Qi cavendish...@gmail.com

 Hi, Ola,

 Just got notification about your question from others, and subscribed
 this mailing list.
 http://lists.qt-project.org/pipermail/interest/2013-November/009878.html

 Your question is valid here in some way. I think you could create a bug
 report in jira.

 There is no focus chain concept when Qt Quick 2 was ready at the
 beginning. We tried to support sth like that in this feature,
 QQuickItem::activeFocusOnTab:

 http://qt-project.org/doc/qt-5.1/qtquick/qml-qtquick2-item.html#activeFocusOnTab-prop

 And it doesn't cover the case like your code, KeyNavigation will not work
 when the Item is disabled itself. You need to maintain the focus chain
 yourself in current code. Maybe we could support it in Qt side in the
 future.

 Regards,
 Liang



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


[Interest] Not possible to connect QTcpSocket::error signal the Qt5-way?

2013-11-22 Thread Ola Røer Thorsen
Hi all,

I've started using the new Qt5 way of connecting signals and slots, to
get errors compile-time instead of runtime. Great stuff.

Here is one I struggle to connect. If you have a QTcpSocket, and want to
handle the error signal in a slot called tcpSocketError, a connect like
this:

connect(tcp_socket_, QTcpSocket::error, this, MyClass::tcpSocketError);


fails, the compiler says

error: no matching function for call to 'MyClass::connect(QTcpSocket*,
unresolved overloaded function type, MyClass* const, void
(MyClass::*)(QAbstractSocket::SocketError))'

All the other signals in QTcpSocket connect fine using the same syntax. So
for now I use the old connect for the error signal, and that works fine.

connect(tcp_socket_, SIGNAL(error(QAbstractSocket::SocketError)),
this, SLOT(tcpSocketError(QAbstractSocket::SocketError)));


Is this a bug in Qt, or did I not use the correct syntax? I recon this has
to do with QAbstractSocket having the error() function as well as an error
signal.

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


Re: [Interest] Not possible to connect QTcpSocket::error signal the Qt5-way?

2013-11-22 Thread Giuseppe D'Angelo

Il 22/11/2013 16:56, Ola Røer Thorsen ha scritto:


fails, the compiler says

error: no matching function for call to 'MyClass::connect(QTcpSocket*,
unresolved overloaded function type, MyClass* const, void
(MyClass::*)(QAbstractSocket::SocketError))'



This is a C++ problem -- unresolved overloaded function type means 
that error() has overloads, and you need to select the right one:



connect(socket,
static_castvoid 
(QTcpSocket::*)(QAbstractSocket::SocketError)(QTcpSocket::error),
this,
Class::method);


HTH,

--
Giuseppe D'Angelo | giuseppe.dang...@kdab.com | Software Engineer
KDAB (UK) Ltd., a KDAB Group company
Tel. UK +44-1738-450410, Sweden (HQ) +46-563-540090
KDAB - Qt Experts - Platform-independent software solutions



smime.p7s
Description: Firma crittografica S/MIME
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest


Re: [Interest] Not possible to connect QTcpSocket::error signal the Qt5-way?

2013-11-22 Thread Thiago Macieira
On sexta-feira, 22 de novembro de 2013 16:56:47, Ola Røer Thorsen wrote:
 Is this a bug in Qt, or did I not use the correct syntax? I recon this has
 to do with QAbstractSocket having the error() function as well as an error
 signal.

You did not use the correct syntax.

The compiler told you that the problem was that you did not select one of the 
overloads. QTcpSocket::error points to multiple functions and you need to 
select one only.

To do that, you need to cast the identifier to a specific signature.

void (QAbstractSocket:: *sig)(QAbstractSocket::SocketError) =
QAbstractSocket::error;
connect(tcp_socket, sig, this, MyClass::tcpSocketError);

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


signature.asc
Description: This is a digitally signed message part.
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest


[Interest] QAbstractItemModel::headerData

2013-11-22 Thread Bill Crocker
Gang:

I have created my own item model by sub-classing QAbstractItemModel.

Functions like rowCount take a parent index so the model
knows for which index it is being asked to return the count.
This is good.

My model is hierarchical and different points in the hierarchy
have a different number of rows and (especially) columns.

So, how come ::headerData is not passed an index so it knows for
which parent index it is being asked to return the data?

I'm using Qt 4.7.1

Bill

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


Re: [Interest] QAbstractItemModel::headerData

2013-11-22 Thread andre
Bill Crocker schreef op 22.11.2013 20:19:
 Gang:
 
 I have created my own item model by sub-classing QAbstractItemModel.
 
 Functions like rowCount take a parent index so the model
 knows for which index it is being asked to return the count.
 This is good.
 
 My model is hierarchical and different points in the hierarchy
 have a different number of rows and (especially) columns.
 
 So, how come ::headerData is not passed an index so it knows for
 which parent index it is being asked to return the data?
 
 I'm using Qt 4.7.1
 
 Bill
 
Because Qt does not support vertical headers for tree models (check 
QTreeView, there is no vertical header there!) and it does not support 
different columns for child items either. While theoretically is should 
be possible (after all, QAbstractItemModel really models a nested grid), 
the views simply do not support it. There are 3rd party add ons that 
provide more sofisticated views that can do this sort of thing, but the 
basic Qt model/view system can't handle that. Qt doesn't even handle 
cell spanning (QAbstractItemModel::span is not used.)

André

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


Re: [Interest] Not possible to connect QTcpSocket::error signal

2013-11-22 Thread Philipp Kursawe
 the Qt5-way?
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary2424312414441479834==

--===2424312414441479834==
Content-Type: multipart/signed; boundary=nextPart6567963.r7pnNChBp8;
micalg=pgp-sha1; protocol=application/pgp-signature

--nextPart6567963.r7pnNChBp8
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset=utf-8

Actually that seems to be more a flawed API when the slot and the
accessor have the same name.
From: Thiago Macieira
Sent: 22.11.2013 17:27
To: interest@qt-project.org
Subject: Re: [Interest] Not possible to connect QTcpSocket::error
signal the Qt5-way?
On sexta-feira, 22 de novembro de 2013 16:56:47, Ola R=C3=B8er Thorsen wrot=
e:
 Is this a bug in Qt, or did I not use the correct syntax? I recon this ha=
s
 to do with QAbstractSocket having the error() function as well as an erro=
r
 signal.

You did not use the correct syntax.

The compiler told you that the problem was that you did not select one of t=
he=20
overloads. QTcpSocket::error points to multiple functions and you need to=
=20
select one only.

To do that, you need to cast the identifier to a specific signature.

void (QAbstractSocket:: *sig)(QAbstractSocket::SocketError) =3D
=09QAbstractSocket::error;
connect(tcp_socket, sig, this, MyClass::tcpSocketError);

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

--nextPart6567963.r7pnNChBp8--

--===2424312414441479834==
Content-Type: text/plain; charset=us-ascii
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

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

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


Re: [Interest] static qt without zlib

2013-11-22 Thread Konrad Rosenbaum
On Friday, Friday 22 November 2013 at 15:09, Tim Blechmann wrote:
 well it is not that i want to completely remove zlib, but i currently
 have too many of them ;)
 
  You might try to use a system zlib, i.e. provide your own copy of zlib
  as the one Qt links to and then use the one linked inside Qt.
 
 i've already tried to compile with -system-zlib, but Qt5Core.lib still
 contains zlib symbols.
 or do i need to/am i able to explicitly specify my zlib when compiling qt?

Exactly, the symbols from the system zlib are now in the statically linked 
QtCore. How about not linking it to your own plugin again and instead using 
the zlib symbols from QtCore?

Zlib is actually pretty compatible, so this will generally work.



Konrad


signature.asc
Description: This is a digitally signed message part.
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest


[Interest] QtQuick - ColorAnimation issue with colors that have alpha

2013-11-22 Thread Preet
Hi,

I use ColorAnimation to animate a color transition on a rectangle
between two states (say ColorA to ColorB). The default color of the
rectangle is A, and it changes to B when a child MouseArea is pressed.

In the case where ColorA is completely transparent (#00abcdef) and
ColorB is completely opaque, the animation from ColorA-ColorB seems
to work fine. The alpha along with RGB components is faded from A to
B. However, when going back from B to A, it seems like the transition
goes something like ColorB-ColorA(no alpha)-Black-ColorA

This doesn't happen if ColorB has any alpha in it. There's a quick
work around by making ColorB nearly opaque (ie. #FEabcdef)

Here's a simple example:
http://pastebin.kde.org/pixaqd47y

I'm on Qt 5.2, somewhere around beta from git. Is this a bug?


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