Changing values of a QMap variable

Swati777999

There's a display of some connected devices on the main window when const is present. If I remove const, this list doesn't appear in the main window. That's all I can say , at this point of time.

jsulm

@Swati777999 This is not enough to give you any concrete solution.
You need to debug the application to see what happens if info is not const. Maybe info does not contain anything?

Swati777999

@jsulm

In the following program taken from tutorialspoint , the value of const. is changed.

#include <iostream>
using namespace std;
int main() {
   const int a = 20;
   const int* b = &a;
   cout<<"old value is"<<*b<<"\n";
   int* c=const_cast<int *>(b);
   *c=40;
   cout<<"new value is"<<*b;
   return 0;
}

It does not seem to be working in the case of QMap [replacing int with QMap]. Can someone give some suggestions?

jsulm

@Swati777999 said in Changing values of a QMap variable:

the value of const. is changed

Yes, you can do dirty tricks like casting away const. But you should really avoid this!
You should rather try to understand what the code is doing and what you need to change. Else you will write spagetti code nobody understands and which breaks easilly!

Swati777999

@jsulm said in Changing values of a QMap variable:

@Swati777999 said in Changing values of a QMap variable:

the value of const. is changed

Yes, you can do dirty tricks like casting away const. But you should really avoid this!
You should rather try to understand what the code is doing and what you need to change. Else you will write spagetti code nobody understands and which breaks easily!

The above code seems not to be working with Qt Classes which has amplified my anxiety. I have already spent a day figuring out what to do with const. , now, it feels another day will go in search of a solution! :'(

VRonin

@Swati777999 said in Changing values of a QMap variable:

The above code seems not to be working with Qt Classes which has amplified my anxiety. I have already spent a day figuring out what to do with const.

If you don't know what const is/does stay miles away from const_cast. As far as you are concerned it does not exist.

If you give us a snippet of code we can work on we might help but at this stage it's impossible for us to assist

J.Hilk

@Swati777999 you have to be very careful wenn using const_cast, it has very limited legit use cases and most cases people use it for is actually undefined behaviour!

Swati777999

@VRonin said in Changing values of a QMap variable:

@Swati777999 said in Changing values of a QMap variable:

The above code seems not to be working with Qt Classes which has amplified my anxiety. I have already spent a day figuring out what to do with const.

If you don't know what const is/does stay miles away from const_cast. As far as you are concerned it does not exist.

If you give us a snippet of code we can work on we might help but at this stage it's impossible for us to assist

Info is a QMap with entries Name & Place in it.

void MainWindow::onConnect(const QMap<QString, QString> &info)
{ QString info_name = Info["Name"]; 
 qDebug()<< "Name before change="<<info_name;  // output : Jaret
 if (info_name == "Jaret")
   {
     model_name = "Jane";
     qDebug()<< "Now Name after change="<<info_name;  // output : Jane
     //Info["Name"]=info_name;   // Error occurs here
   }

VRonin

Here info is passed as a read only. You can consider it even a temporary if you want but it stops existing at the end of the function so changing it makes little sense.

where does info come from? is it a member of some other class?

jsulm

@Swati777999 said in Changing values of a QMap variable:

void MainWindow::onConnect(const QMap<QString, QString> &info)

It should be clear (C++ basics) that if you want to change info inside that method you have to make it non-const:

void MainWindow::onConnect(QMap<QString, QString> &info)

VRonin

@jsulm said in Changing values of a QMap variable:

void MainWindow::onConnect(QMap<QString, QString> &info)

Yeah but it looks like a slot so this is probably not the right way to go about changing its contents

Swati777999

@VRonin said in Changing values of a QMap variable:

@jsulm said in Changing values of a QMap variable:

void MainWindow::onConnect(QMap<QString, QString> &info)

Yeah but it looks like a slot so this is probably not the right way to go about changing its contents

If I make it non-const, then it is giving unrelated results. So, I tried for const_cast conversion, and that too seemed not to be working with Qt classes. Any suggestions that you would like to give?

mrjj

@Swati777999

Hi
You must change both .cpp and .h to
for
void onConnect(QMap<QString, QString> &info)

That is - to remove the const so you can modify "info" in the method.
Both places.

Then this syntax will work
Info["Name"]=info_name;

Fooling around with const_cast wont bring anything good.

Simply just allow "info" to be changed removing the const is the way to go :=)

and maybe you need to fix up some signal if used with it and it also list info as const.

Swati777999

@mrjj said in Changing values of a QMap variable:

@Swati777999

Hi
You must change both .cpp and .h to
for
void onConnect(QMap<QString, QString> &info)

That is - to remove the const so you can modify "info" in the method.
Both places.

Then this syntax will work
Info["Name"]=info_name;

Fooling around with const_cast wont bring anything good.

Simply just allow "info" to be changed removing the const is the way to go :=)

It is not working. I've already tried it in this way and it is showing the undesired result as discussed in my previous comments. It's the first thing that I tried. This is a slot function used twice in my program as private and public slot.

and maybe you need to fix up some signal if used with it and it also list info as const.

Thanks for this suggestion. This had not struck me before. I will try it this way.

Swati777999

@jsulm said in Changing values of a QMap variable:

@Swati777999 said in Changing values of a QMap variable:

void MainWindow::onConnect(const QMap<QString, QString> &info)

It should be clear (C++ basics) that if you want to change info inside that method you have to make it non-const:
void MainWindow::onConnect(QMap<QString, QString> &info)

Tried it in both header and source file and the result comes out to be undesirable.

jsulm

@Swati777999 @VRonin asked you where info comes from: can you please answer this question? It sounds somewhat strange if a slot changes its parameters content.