Add New..., Add Existing Files..., Add Existing Directory... all greyed out in a qMake project

aha_1980

Yup I deleted the .user file (and all its clones) and that didn't seem to have any affect.

that (clones) sounds as if you opened the project with different Creator versions. that can indeed lead to corrupted compiler settings for the project. especially 'downgrades' seem problematic.

mrjj

@aha_1980
Oh good spotted. I totally missed the cloned part.

Rlkcpo

I only have one version of creator. I assumed the clones were some function of the software. I end up with:

project.pro.user
project.pro.user.b34a037
project.pro.user.a256d45
etc

This might be why I continue to lose my settings between sessions. (I end up having to delete everything in the ~/.config/ directory to clear it.)

mrjj

@Rlkcpo

Hmm that is a bit odd then as it how it has multiple .user files.
if you only use one Creator then im not sure what is going on then.
and yes, a new .user file forgets all settings from the old.

Rlkcpo

Hmmm ok im going to mark this as unsolved again. It seems as if the problem is back and this time the compilers are not the problem. Again my ability to add files/directories is greyed out.

I think maybe at this point im getting a bit disillusioned about Qt. I think there is some kind of link to a previously installed version of Qt on this work machine...but for the life of me I cannot find it to remove it.

mrjj

Hi
I assume you on some linux?
So this time when GREY happened, there was not extra .pro.user.xxxx files?

Check the icon for Creator (in menu/bar) that it links to the right place.
and not run qtchooser but directly links to qtcreator in the Qt install folder.

Also change the theme in Creator so if another should popup you can spot in on colors.

I assume you tried
sudo updatedb
locate qtcreator
and found only one ?

Also, you are not using same project from different user profiles ?

aha_1980

Hi @Rlkcpo,

I only have one version of creator. I assumed the clones were some function of the software. I end up with:
project.pro.user
project.pro.user.b34a037
project.pro.user.a256d45

Ok, these backups are not because of a different version, but because of a different Kit setup. Usually this happens if you open the project with Creators from different computers (e.g. if it is on a network share). It can also happen if you check in the *.pro.user into version control.

This might be why I continue to lose my settings between sessions.

No, it's rather other way round.

(I end up having to delete everything in the ~/.config/ directory to clear it.)

Ah-ha! This will possible change your kit settings and therefore the *.pro.user becomes invalid.

The questions if rather, what makes your settings in the .config directory invalid? Today I had an effect that may be related. We had several Creator windows open and added a manual Qt version including debugger and compiler. We did save the setting, but it seems it was overwritten after the last Creator (which did not have this setting) was closed.

So this is my tip: if you need to change Kit settings, have only one instance open and close it after you changed the setting. Then everything should be fine.

Rlkcpo

@mrjj said in Add New..., Add Existing Files..., Add Existing Directory... all greyed out in a qMake project:

Hi
I assume you on some linux?
So this time when GREY happened, there was not extra .pro.user.xxxx files?

Check the icon for Creator (in menu/bar) that it links to the right place.
and not run qtchooser but directly links to qtcreator in the Qt install folder.

Yes I am running Ubuntu 16.04 and the shortcut is linking to the correct qtcreator executable.

Also change the theme in Creator so if another should popup you can spot in on colors.

Yup been running the dark theme to quickly spot when this occurs.

I assume you tried
sudo updatedb
locate qtcreator
and found only one ?

Correct there is only one version.

Also, you are not using same project from different user profiles ?

Nope. Im the only one on this machine (for the time being).

yugiquan

I have the same problem. The reason is use cmake (maybe you use cmake?? check it). I use qmake to fix it.

weilu

Hi @yugiquan
How do you fix this problem？(I have the same question and use cmake)

Narek

@weiluI also ran into this problem. I couldn't find a solution to this problem. If you find one, could you explain it? I can add files manually through CMakeLists.txt, but I'd prefer to add them without it