QML and Qt Quick

This may not be the best way but what you could try to do is create an OpenGL context using a fake, high version and then check what was actually created. In QOpenGLContext's docs: "If the OpenGL implementation on your system does not support the requested version of OpenGL context, then QOpenGLContext will try to create the closest matching version." Example: @QSurfaceFormat requestedFormat; requestedFormat.setVersion( 99, 99 ); QOpenGLContext* context = new QOpenGLContext; context->setFormat( requestedFormat ); context->create(); qDebug() << QString("Requested OpenGL version (%1.%2); Actual created version (%3.%4).").arg(requestedFormat.majorVersion()).arg(requestedFormat.minorVersion()).arg(context->format().majorVersion()).arg(context->format().minorVersion());@

Because I didn't know it :-) It seems it fits perfectly for my needs, thanks.

The velocity just defines how fast the GridView should flick. You cannot set to which position it should flick as far as I know.

Ok! I've found the solution. The first you need to create the Objective-C class which will implement all logic to methods: header file (notificationmanager.h) of ObjC: @ #ifndef NOTIFICATIONMANAGER_H #define NOTIFICATIONMANAGER_H #ifdef __cplusplus extern "C" { #endif #import <Foundation/Foundation.h> @interface NotificationManager : NSObject (instancetype)init; (void)postNotificationWithTitle:(NSString*)title message:(NSString*)msg; (BOOL)isObjectCreated; (NotificationManager*)defaultManager; (void)clearAllDatas; @end #ifdef __cplusplus } #endif #endif // NOTIFICATIONMANAGER_H @ the implementation (notificationmanager.mm) of ObjC: @ #include "notificationmanager.h" #include <QtCore> @interface NotificationManager () <NSUserNotificationCenterDelegate> @end @implementation NotificationManager static NotificationManager* g_notificationManager = nil; (instancetype)init { self = [super init]; if(self) { [[NSUserNotificationCenter defaultUserNotificationCenter] setDelegate:self]; } return self; } (void)postNotificationWithTitle:(NSString*)title message:(NSString*)msg { NSUserNotification* notification = [[NSUserNotification alloc] init]; notification.title = title; notification.informativeText = msg; [[NSUserNotificationCenter defaultUserNotificationCenter] deliverNotification: notification]; } (BOOL)isObjectCreated { return (g_notificationManager != nil); } (NotificationManager*)defaultManager { if(!g_notificationManager) { g_notificationManager = [[NotificationManager alloc] init]; } return g_notificationManager; } (BOOL)userNotificationCenter:(NSUserNotificationCenter *)center shouldPresentNotification:(NSUserNotification *)notification { Q_UNUSED(center); Q_UNUSED(notification); return YES; } (void)clearAllDatas { [g_notificationManager release]; g_notificationManager = nil; } (void)dealloc { [super dealloc]; qDebug()<<"Object released!!!!"; } @end @ Second you need create C++ class with .mm file implementation (qfnotificationmanager.h): @ #ifndef QFNOTIFICATIONMANAGER_H #define QFNOTIFICATIONMANAGER_H #include <QtCore> #ifdef __cplusplus extern "C" { #endif class QfNotificationManager : public QObject { // Q_OBJECT public: explicit QfNotificationManager(QObject *parent = 0); ~QfNotificationManager(); static QfNotificationManager* defaultManager(QObject *parent = 0); void postNotification(QString title, QString message); signals: public slots: }; #ifdef __cplusplus } #endif #endif // QFNOTIFICATIONMANAGER_H @ and implementation (qfnotificationmanager.mm): @ #include "qfnotificationmanager.h" #include <Foundation/Foundation.h> #include "notificationmanager.h" static QfNotificationManager* g_notificationManager = NULL; QfNotificationManager::QfNotificationManager(QObject *parent) : QObject(parent) { [NotificationManager defaultManager]; } QfNotificationManager::~QfNotificationManager() { [[NotificationManager defaultManager] clearAllDatas]; } QfNotificationManager* QfNotificationManager::defaultManager(QObject *parent) { if(!g_notificationManager) { g_notificationManager = new QfNotificationManager(parent); } return g_notificationManager; } void QfNotificationManager::postNotification(QString title, QString message) { NSString* objcTitle = title.toNSString(); NSString* objcMessage = message.toNSString(); [[NotificationManager defaultManager] postNotificationWithTitle: objcTitle message: objcMessage]; } @ How to use (from .cpp file you need to call this): @ QfNotificationManager::defaultManager(this); QfNotificationManager::defaultManager()->postNotification("Qt Forum Reader", "This is test notification message"); @

Hi beenmanenl, i haven't found my code. Sorry.

[quote author="aabc" date="1413206015"]If I have 12 QML pages that loads dynamically, each page contain ~400 MyText elements - Do you think that in this case the pages will be loaded faster if I use the MyText element instead of using Text element and give it the properties ?[/quote] Please benchmark it, I don't know. I guess the difference would not be substantial, but that is a guess. QML enigne provides a lot of flags that can be used in debugging. You can get in touch with QML developers (see maintainers list here on Qt Project website) to get more concrete answers. Or ask on Qt interest mailing list/ IRC.

In general, the Menu seems unreasonable and closed, with no prospect of enlargement. Impossible to know the geometry of the menu window before it opens. I am disappointed implementation of Menu.

How can I determine if my rendering target is 32 bit or 16 bit ?

That makes sense then. I've noticed the same behaviour on OSX as well, when attaching the MacBook to a projector for instance. There are a few different problems causing this problem. The root cause is that the OS and windowing system blocks in OpenGL's swapBuffers based on the vsync of only one screen (the primary display in this case) rather than for the display the window displayed on. Qt's animation system is also ticked globally, not per window (except for the Animator classes when using threaded rendering). That means that even if the system were to support it, we still couldn't do individual frame rates on two separate displays. I'm also not sure that is desired. It would have a lot of side effects...

I see. Thank you. :)

Hi, IIRC, the first one applies to the old Qt3d module (which was never officially released) while the other to the QGraphicsView and friends part of Qt Base. If you are interested by the Qt3d module, you should rather check the wip/newapi branch. Hope it helps

Hi, The qmllistproperties work slightly in a different way than regular. You need to implement a number of static functions to get everything working. Check the documentation, it has examples to get you started!

OK, I got it! Thanks very much. :)

Maybe "here":https://qt.gitorious.org/qt/qtdeclarative/source/29c4b643272a43022081cce063394bac823ab529:examples/declarative/particles/trails/fireworks.qml near the end of the file.

It works! Thank you!