dbus-1-tqt does not support array of objectpathkeymaps #1

https://bugs.trinitydesktop.org/show_bug.cgi?id=2925

When trying to parse data with signature a{oa{sa{sv}}} the flow is something like this:

TQT_DBusProxy::sendWithReply
-> TQT_DBusConnection::sendWithReply
-> TQT_DBusMessage::fromDBusMessage(reply)
-> TQT_DBusMarshall::messageToList(message, dmsg)
-> qFetchParameter(&it)
-> TQT_DBusData qFetchMap
-> qFetchStringKeyMapEntry

It turned out that it does not support array of objectpathkeymaps and it was returning a null key, which explains why it was returning always the last entry

The code looks good. It does not seem to cause any change to the API / ABI. Please, just a little cleaning.

Note: Please remove the test output as an ammend of an existing commit and then use push with -f.

@deloptes, please do the small cleaning as mentioned in the review above.

Hi Slavek,
sorry for the multiple commits, I tried for first time the ammend but failed miserably :)

regards

All right, it does not matter – I did squash to combine your series of commits into one 😸

 //            dbus_message_iter_get_fixed_array(&sub,&data,&len);
 //            return TQCString(data,len);
 //         } else {

     Q_ASSERT(dbus_message_iter_has_next(&itemIter));
     TQString key = qFetchParameter(&itemIter).toString();
 //	tqDebug("qFetchStringKeyMapEntry key : %s", key.latin1());