Re: [Development] A QtCore class for event-driven jobs

Op 11-9-2013 17:19, David Faure schreef: >> Couldn't such a class be part of the hopefully coming QtConcurrent >> replacement? > Can we forget about threads for a second? No, I'd rather not forget that huge pink elephant in the room... In this age of multi-core systems being the norm rather than e

Re: [Development] [Releasing] HEADS UP: Starting preparations for Qt 5.2.0 - merge 'dev' into 'stable'

Hi, Could you please let me know if Qt3d repository to be part of Qt5.2? Thanks and Regards, Ramakanth -Original Message- From: releasing-bounces+ramakanthreddy_kesireddy=mahindrasatyam@qt-project.org [mailto:releasing-bounces+ramakanthreddy_kesireddy=mahindrasatyam@qt-project.

Re: [Development] constexpr and qMetaTypeId<>()

On quarta-feira, 11 de setembro de 2013 14:29:44, achart...@fastmail.fm wrote: > Hello, > > I'd like to use qMetaTypeId<>() in a constexpr expression. You can't. The types are registered at runtime. > Any help is greatly appreciated. -- Thiago Macieira - thiago.macieira (AT) intel.com Softw

Re: [Development] [Feature] Q_INFO: Annotations for classes, methods, properties and enums

On quarta-feira, 11 de setembro de 2013 22:19:33, Stefan Merettig wrote: > This would be ambiguous to the reader. That's why I always stressed > that the > macro is *prepended* to whatever it applies to: > >Q_ANNOTATE("foo" = "bar") class MyClass { ... I'm fine with that, provided it matches

Re: [Development] [Feature] Q_INFO: Annotations for classes, methods, properties and enums

On quarta-feira, 11 de setembro de 2013 12:03:52, Matt Broadstone wrote: > On Wed, Sep 11, 2013 at 2:33 AM, Olivier Goffart wrote: > > Q_INFO("foo", "bar") > > Q_PROPERTY(int bar READ bar) > > Q_INFO("foo", "baz") > > Q_PROPERTY(int baz READ baz) > > > > > > Q_PROPERTY(int bar READ bar INFO "

Re: [Development] [Feature] Q_INFO: Annotations for classes, methods, properties and enums

On Wednesday 11 September 2013 07:41:03 Saether Jan-Arve wrote: > I think "foo" = "bar" is easier to read. > Why not use the same syntax for the regular Q_INFO annotations too: > Q_INFO("foo" = "bar") > > I also think that the name Q_INFO is way too generic (everything in a source > file is inform

[Development] New SceneGraph related issue

Hi, I have strange issue running most recent Qt sources on Tizen emulator (qemu i586). Also I know that there are issues with supporting HW acceleration. For example I need to export QML_BAD_GUI_RENDER_LOOP=1 because multithreaded OpenGl is a little broken there. Anyway: When I run simple Qml App

Re: [Development] [Feature] Q_INFO: Annotations for classes, methods, properties and enums

>2013/9/11 Olivier Goffart : >> Alright guys, let's try to complete the feature. As I heard from sides >> now that you want a key-value store, I'll do it that way. >> >> Feature list: >> 1. Q_INFO is a new macro (which expands to nothing): >>#define Q_INFO(key, value) > > Since we have Q_CLASSI

[Development] constexpr and qMetaTypeId<>()

Hello, I'd like to use qMetaTypeId<>() in a constexpr expression. I have my own custom type declared as such: class MyCustomClass : public QObject { Q_OBJECT // ... }; Q_DECLARE_METATYPE(MyCustomClass*) I then try the following: constexpr qint32 metaTypeId = qMetaTypeId(); static_as

Re: [Development] [Feature] Q_INFO: Annotations for classes, methods, properties and enums

Am 11.09.2013 21:49, schrieb Thiago Macieira: > On quarta-feira, 11 de setembro de 2013 12:03:52, Matt Broadstone > wrote: >> Q_ANNOTATE(bar, foo = "baz", abc = "cde") >> (this annotates the aforementioned property, and is a specialization >> of the >> "normal" Q_ANNOTATE, and can appear anywher

Re: [Development] [Feature] Q_INFO: Annotations for classes, methods, properties and enums

Hi, >From the whole discussion, this is what I believe it should look like: class Foo { /* For class annotations, we keep the Q_CLASSINFO as it is */ Q_CLASSINFO("foo", "bar") /* For properties, we put the annotation in the property macro */ Q_PROPERTY(int foo READ foo ANNOTATE foo =

Re: [Development] [Feature] Q_INFO: Annotations for classes, methods, properties and enums

On Wed, Sep 11, 2013 at 2:33 AM, Olivier Goffart wrote: > Hi, > > Great to see we are making progress. > > On Tuesday 10 September 2013 18:26:09 Stefan Merettig wrote: > > Alright guys, let's try to complete the feature. As I heard from sides > > now that you want a key-value store, I'll do it th

[Development] Qt5::lrelease path issues (QTBUG-32570)

Using qttools-5.1.1... In short, Qt5LinguistToolsConfig.cmake ends up defining Qt5::lrelease to point to /usr/lib64/cmake/Qt5LinguistTools/bin/lrelease instead of /usr/lib64/qt5/bin/lrelease It would appear this was supposed to be fixed in 5.1.1, https://bugreports.qt-project.org/browse/QTBUG-32

Re: [Development] A QtCore class for event-driven jobs

On Tuesday 10 September 2013 21:09:55 Peter Kümmel wrote: > On 06.09.2013 19:52, David Faure wrote: > > connect(job, SIGNAL(result(QJob*)), > > this, SLOT(handleResult(QJob*))); > > This looks so old-school like in times of futures and monads. I'm an old-timer, clearly ;-) > Coul

Re: [Development] HEADS UP: Starting preparations for Qt 5.2.0 - merge 'dev' into 'stable'

On quarta-feira, 11 de setembro de 2013 12:42:50, Sergio Ahumada wrote: > - After Sept 23rd any changes that are required for 5.2.0 need to be > pushed to the 'stable' branch. So if your changes are not in by that > day, please wait until the merge is done and re-target it to the > 'stable' branch.

Re: [Development] Fwd: [Interest] QAbstractEventDispatcher

On quarta-feira, 11 de setembro de 2013 11:19:29, Phil Hannent wrote: > Good morning, > > I am attempting to use a Glib based library with Qt, it works > perfectly on Linux but on windows the application locks up. > > I have gotten as far as realising that I need to use the > QAbstractEventDispat

Re: [Development] HEADS UP: Starting preparations for Qt 5.2.0 - merge 'dev' into 'stable'

On 09/11/2013 01:14 PM, Blasche Alexander wrote: > Hi, > > Prior to this merge, will you merge stable into dev? It hasn't happened at > least for qt5.git so far. > -- > Alex > Hi, I merged stable->dev last Friday for most of the modules

Re: [Development] HEADS UP: Starting preparations for Qt 5.2.0 - merge 'dev' into 'stable'

Hi, Prior to this merge, will you merge stable into dev? It hasn't happened at least for qt5.git so far. -- Alex From: development-bounces+alexander.blasche=digia@qt-project.org [development-bounces+alexander.blasche=digia@qt-project.org] on beha

[Development] HEADS UP: Starting preparations for Qt 5.2.0 - merge 'dev' into 'stable'

Hi, We are starting the preparations for the Qt 5.2.0 release, which means that: - We plan to merge 'dev' into 'stable' branch on September 23rd. - After Sept 23rd any changes that are required for 5.2.0 need to be pushed to the 'stable' branch. So if your changes are not in by that day, please

[Development] Fwd: [Interest] QAbstractEventDispatcher

Good morning, I am attempting to use a Glib based library with Qt, it works perfectly on Linux but on windows the application locks up. I have gotten as far as realising that I need to use the QAbstractEventDispatcher, that the qeventdispatcher_glib.cpp and qeventdispatcher_win.cpp provide good e

Re: [Development] qt installer - user register access

Hi Richard, at the moment this usecase is not implemented and a shortcut to get the list via the installer.value functions sounds wrong to me. So please create a feature request for that at jira. As a workaround you can use the execute feature: registryCallOutput = installer.execute("reg", ne

Re: [Development] [Feature] Q_INFO: Annotations for classes, methods, properties and enums

> -Original Message- >> Other people have suggested adding the info to the Q_PROPERTY >> expansion. >> This would avoid a sequence of Q_INFO / Q_PROPERTY pairs in the >> class that might be difficult to read: >> >> Q_INFO("foo", "bar") >> Q_PROPERTY(int bar READ bar) >> Q_IN