Hello,
and what is your question? What do you get and what do you expect?
I have to guess a little bit: Your program compiles fine and when you run it on linux, you see only some debug messages output by your program, but not the tree you expect. Now let's have a look at QObject::dumpObjectInfo() documentation:
Dumps information about signal connections, etc. for this object to the debug output.
This function is useful for debugging, but does nothing if the library has been compiled in release mode (i.e. without debugging information).
Here library refers to the Qt library containing QObject. If you use Qt from your ubuntu repository, the Qt libraries are by default compiled in release mode and therefore, according to the documentation, you get no output. Note that this does not change if you build your code in debug mode!
I ran your program under Windows, where we have a set of debug and release libraries. Here I get the following output in debug build (for depth 3):
filling
Filled
OBJECT foo::unnamed
SIGNALS OUT
<None>
SIGNALS IN
<None>
foo::
foo::
foo::
foo::
foo::
foo::
foo::
dumped
filling
Filled
OBJECT foo::unnamed
SIGNALS OUT
<None>
SIGNALS IN
<None>
foo::
foo::
foo::
foo::
foo::
foo::
foo::
dumped
To copy to clipboard, switch view to plain text mode
Possibly not what you expected. You get information about signal/slot connection and not about your member objects. I'm afraid you have to write your own recursive dump function for outputting your S and D settings.
Best regards
ars
Bookmarks