Re: [Interest] Fwd: Qt 5.7+ and Command+Shift shortcuts on Mac

2017-01-08 Thread Albert Astals Cid
El divendres, 6 de gener de 2017, a les 21:29:13 CET, René J.V. Bertin va escriure: > On Friday January 06 2017 18:33:01 David Faure wrote: > > Well, you didn't say either way, so I tried to guess from your > > description, > > and guessed wrong. > > No problem, can't be right all the time (and

[Interest] How to improve Qt's QSS/CSS performance on embedded devices?

2017-01-08 Thread Michael Herzlich
Hi Qt developers,   I ran into performance problems with Qt for embedded Linux 4.8.3 on custom hardware. The styling of the UI is done with QSS and no custom painting code. There are multiple measurements visualized in this post in the Qt-forum:

Re: [Interest] Qt 5.7+ and Command+Shift shortcuts on Mac

2017-01-08 Thread Samuel Gaist
> On 8 Jan 2017, at 19:09, René J.V. Bertin wrote: > > So... > > It seems we are indeed looking at a Qt regression. > > https://github.com/RJVB/shortcut-test-qt5 > > > That's an adapted version of Qt's menus example which adds a shortcut test > action with a

Re: [Interest] Fwd: Qt 5.7+ and Command+Shift shortcuts on Mac

2017-01-08 Thread René J . V . Bertin
So... It seems we are indeed looking at a Qt regression. https://github.com/RJVB/shortcut-test-qt5 That's an adapted version of Qt's menus example which adds a shortcut test action with a configurable shortcut string and commandline options to add it to the menubar and/or the context menu,

Re: [Interest] including kde classes in qt

2017-01-08 Thread Kevin Funk
On Sunday, 8 January 2017 12:54:03 CET mayank bansiwal wrote: > hello mates. > i have just started to code with qt creator. I want to contribute to kde > open source organization which uses qt. Can anyone please tell me how to > include kde classes in qt ide. I added this syntax in my .pro file >

Re: [Interest] including kde classes in qt

2017-01-08 Thread Jean-Michaël Celerier
You also have to include the path to the header. However I think that the KDE organization is centered on CMake instead of qmake (another way to specify the build of your library). See here : https://community.kde.org/Guidelines_HOWTOs/CMake (and more generally, before contributing to KDE,