Return QObject undefined

[wysota]

I added this to main().

qmlRegisterType<Object2>("com.test.object", 1, 0, "Object2");

qmlRegisterType<Object2>("com.test.object", 1, 0, "Object2");

To copy to clipboard, switch view to plain text mode 

[coderbob]

I error with:

In file included from object1.h:6,
from main.cpp:7:
object2.h:21: error: explicit specialization in non-namespace scope ‘class Object2’
object2.h:21: error: ‘struct QMetaTypeId<Object2*>’ redeclared with different access
object2.h:21: error: explicit specialization in non-namespace scope ‘class Object2’
object2.h:21: error: ‘struct QMetaTypeId<QDeclarativeListProperty<Object2> >’ redeclared with different access
make: *** [main.o] Error 1

[wysota]

I don't know what you did exactly to get this error but the line I gave you is the only change I made to the whole program (apart including headers for your classes, of course).

#include "object1.h"
#include "object2.h"
 
int main(int argc, char *argv[])
{
  QApplication app(argc, argv);
 
  QDeclarativeView view;
  qmlRegisterType<Object2>("com.test.object", 1, 0, "Object2");
   view.setResizeMode(QDeclarativeView::SizeRootObjectToView); 
 
   Object1 *object1 = new Object1();
 
   view.rootContext()->setContextProperty("myObject1",object1);
 
   view.setSource(QUrl::fromLocalFile("main.qml"));
   view.show();
 
  return app.exec();
}

#include "object1.h"
#include "object2.h"

int main(int argc, char *argv[])
{
  QApplication app(argc, argv);

  QDeclarativeView view;
  qmlRegisterType<Object2>("com.test.object", 1, 0, "Object2");
   view.setResizeMode(QDeclarativeView::SizeRootObjectToView); 

   Object1 *object1 = new Object1();

   view.rootContext()->setContextProperty("myObject1",object1);

   view.setSource(QUrl::fromLocalFile("main.qml"));
   view.show();

  return app.exec();
}

To copy to clipboard, switch view to plain text mode 

[coderbob]

Thank you Wysota, the problem I was having was experimenting with other possibilities and I did not back that code out before attempting the qmlRegisterType.

I have noticed that QML behaves differently when these objects are passed to the script as a signal. I have added to the previous code example that reproduces this.

The update adds a singleShot QTimer that passed the object1 twice to the script. Once declared class and the second as a QObject.

When passed as a class it is casted as a QVariant and I will not have access to any properties or slots.

When passed as a QObject I will have access to properties but is also casted differently then when it is passed using the doSomething() function. (Clickign anywhere in the window)

I could not find anyway to cast it from a QVariant in the script so I could access it properly. Also a little confused why it is casting the same object type differently.

[coderbob]

Appears to be a bug. Filed as http://bugreports.qt.nokia.com/browse/QTBUG-15712

[wysota]

Appears to be a bug. Filed as http://bugreports.qt.nokia.com/browse/QTBUG-15712

Where do you see the bug? Your code works fine if you register the types properly - with qml, with qvariant and with the signal/slots system.

[coderbob]

Wysota, please review the second code example more closely. Also follow the link in the report to the thread on the dev site.

To put it simply all 3 returned objects are casted differently.

[wysota]

I don't know how much more closely can I review the code. I don't know what doesn't work for you, to be honest. For me your application simply works, I can print the object name of the object returned by Object1::getObject2() just fine. What exactly is the "bug" you see?

[coderbob]

2 Signals are emitted and pass a QObject to the QML/js code. Both of these signals are interpreted by a single js function doSomething().

This first signal is defined as void mySignalSpecific(Object1 *obj); and is passing as a defined class.

The second is defined as void mySignalQObject(QObject *obj); and is passing as a QObject.

Both of these produce different results inside the function doSomething();

void mySignalSpecific(Object1 *obj) outputs:

QVariant(Object1*)
undefined

here we do not have access to myObject1.getObject2(); Also I did not see anywhere in the docs of how I could cast a QVariant in QML/js to be able to access it correctly.

void mySignalQObject(QObject *obj) outputs:

Object1(name = "")
object1 name property

and all works as intended. Right here you can see that the class is being casted differently when it is the same object. This method forces qcasting inside the c++ code or a separate function.


The third output when using view.rootContext()->setContextProperty("myObject1",object1); to give access to the object outputs.

Object2(0x69fc60)


Now the third example is not signal based but still shows how the same object is being casted differently when it should not be.

[wysota]

And please show me where in your code did you tell QVariant how to handle Object1* and where did you tell the signal/slot system how to treat Object*. How should QVariant know it should cast its data to Object1* when passing it through signals and slots?

I completely don't understand what is wrong with what you refer to as "third example". What is cast differently than what?

[coderbob]

And please show me where in your code did you tell QVariant how to handle Object1* and where did you tell the signal/slot system how to treat Object*. How should QVariant know it should cast its data to Object1* when passing it through signals and slots?

I am not sure where we are miss communicating here but your reply is explaining the problem.

First Object1 is a descendant of QObject which already puts it in the meta system. Secondly it is registered with qmlRegisterType<Object1>("com.test.object1", 1, 0, "Object1"); for QML.

Thirdly there is no reason it should be casted as a QVariant. This has been acknowledged by nokia and it is a lack of code in the signal/slot system related to QML.

If you can alter the code and make it work properly in 3 of the 3 examples instead of 2 it might help bridge the gap of the misunderstanding.

[wysota]

I am not sure where we are miss communicating here but your reply is explaining the problem.

First Object1 is a descendant of QObject which already puts it in the meta system.

Meta-system - yes. Signals and slots - no.

Secondly it is registered with qmlRegisterType<Object1>("com.test.object1", 1, 0, "Object1"); for QML.

QML - yes. Signals and slots - no.

Thirdly there is no reason it should be casted as a QVariant.

Sure there is. All custom things in Qt go through QVariant and signals and slots use QVariant as means for data storage with queued connections.

If you can alter the code and make it work properly in 3 of the 3 examples instead of 2 it might help bridge the gap of the misunderstanding.

I spent half an hour trying to understand your "simple" example so I'm definitely not going to alter it now. I still don't understand what your problem is. Your program outputs something but how should I know what you consider "correct" or not. If you want a simple example, have your program output three strings in the format "is: %1, should be %2". Then we can work on fixing the problem.