Problem with QMap

[mrjj]

Ok, it does look perfect valid.

have you tried
qDebug() << size(); (in ctor)
and
qDebug() << par.size(); (right after u define par)

[cristiano.narcisi]

Ok. But what does it happen when the function is contains(..key..)?

[mrjj]

@cristiano.narcisi
it looks like outside of constructor the key list is no more.
i wanted to see if it says
zero for par.

[cristiano.narcisi]

@mrjj

Ok but it is very strange. I give you another information: i can view all the key-value pair stored into the par variable using the watches of the editor!!!!

[mrjj]

@cristiano.narcisi
OK ?!?! That also pretty strange.

what about size inside and out?

[cristiano.narcisi]

@mrjj

Size outside the ctor is correct. It is 5!!!

[cristiano.narcisi]

Using the iteartor i can view all the values stored in the QMap .... Probably i don't understand something of very important about how QMap acceses the data.
//your code here

 QMap<const char *, QString>::ConstIterator ii;
 for( ii = par.constBegin(); ii != par.constEnd(); ++ii )
   qDebug() << ii.key() << " = " << ii.value();```

[mrjj]

@cristiano.narcisi
ok ?!?

I think you should try dump the list using par to see if key corruption
else there is no reason contains should not work.

[cristiano.narcisi]

@mrjj

Probably i have understood why i can retry the key. The problem is that i am using

QMap< const char *, QString> 

This means that the key is a POINTER and not the text !!!

I have replaced the QMap template with

QMap< QString, QString>

Now the key is an ITEM and not a POINTER and i can find all the keys and the value stored within the QMap.

Sorry for bothering you

Thanks for hepling me

Regards

Cristiano Narcisi

[kshegunov]

@mrjj

Inheriting from Qmap is a bit funky

It's specially noted in the docs that deriving from a container specialization is not recommended. That's probably what seems funky ;)

[mrjj]

@cristiano.narcisi
ok so
#define MAC_KEY "mac"
used as key did funky stuff?

good found :)

[kshegunov]

@mrjj said:

used as key did funky stuff?

The only funky stuff with that macro is that char * doesn't have a meaningful operator <, which is required for it to be a key in the map. The comparison is done as you'd compare integers.