Luca wrote:

1. QString my_global_string;
2. ..
3. ...
4. main(...)
5. {
6. ...
7. my_global_string = QString  ("ciao");
8. ...
9. MyClass my_class;
10. ...
11.  
12. return a.exec();
13.  
14. }

1. MyClass::MyClass()
2. {
3. ...
4. qDebug() << my_global_string;
5. ...
6. }

That should do the trick. Move the declaration out of your main routine.

I need to “see” the variable in other .cpp file too.

Than you have to use an extern statement in the other source file

I am trying to find a link to support you.

This elaborates on the issue: extern variable [en.wikipedia.org]

Personally, I dislike global variables. I find there are really no good use cases for them. What you can do instead, is use QApplication to hold your application wide data. You can either:

• Subclass QApplication, and give it proper access methods to your data, or
• Use Qt’ s dynamic property feature to just set a QVariant property on your QApplication object

However, it is just a personal dislike. The language supports it (and Qt does nothing that constrains your use of it), so go right ahead if you must.

Andre wrote:

Personally, I dislike global variables. I find there are really no good use cases for them. What you can do instead, is use QApplication to hold your application wide data. You can either:

• Subclass QApplication, and give it proper access methods to your data, or
• Use Qt’ s dynamic property feature to just set a QVariant property on your QApplication object

However, it is just a personal dislike. The language supports it (and Qt does nothing that constrains your use of it), so go right ahead if you must.

Thanks Andre,
I used a property on QApplication object this way:

and it do the works!

Andre wrote:

Personally, I dislike global variables. I find there are really no good use cases for them. What you can do instead, is use QApplication to hold your application wide data. You can either:

• Subclass QApplication, and give it proper access methods to your data, or
• Use Qt’ s dynamic property feature to just set a QVariant property on your QApplication object

However, it is just a personal dislike. The language supports it (and Qt does nothing that constrains your use of it), so go right ahead if you must.

Andre, you are raising certainly a valid point with your response.

Global variables have always some “smell” of the old “FORTRAN common block”. Hard to controll because completely confusing when you are looking for the place changing some part of your data.

One must have no other alternative when using global variables. Otherwise they may be the start of disaster.