Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Get Qt Extensions
  • Unsolved
Collapse
Brand Logo
  1. Home
  2. Qt Development
  3. General and Desktop
  4. Add New..., Add Existing Files..., Add Existing Directory... all greyed out in a qMake project
Forum Updated to NodeBB v4.3 + New Features

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

Scheduled Pinned Locked Moved Unsolved General and Desktop
18 Posts 5 Posters 10.7k Views 3 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • R Offline
    R Offline
    Rlkcpo
    wrote on 30 Jan 2018, 19:06 last edited by
    #1

    Hello everyone,

    So strange issue I ran into today, basically my project no longer allows me to add files/directories. I did a quick search and found some bugs with this problem back with Creator 2.7 but the issue seems to have been solved long ago.

    So I am running QT 5.10 with Creator 4.5
    This is a fresh install (Im evaluating Qt for work) with a fresh project (simple adding a directory structure for eventual code/unit testing ). It was as I was adding this structure that the problem occurred. If I create a new project the issue disappears and I can add freely again.

    So what would cause any particular project to exhibit this behavior?

    1 Reply Last reply
    0
    • M Offline
      M Offline
      mrjj
      Lifetime Qt Champion
      wrote on 30 Jan 2018, 19:12 last edited by
      #2

      Hi
      I have only seen this one time where it would hang while parsing the
      .pro file upon open the project.
      Anything fancy in the .pro file ?

      1 Reply Last reply
      0
      • R Offline
        R Offline
        Rlkcpo
        wrote on 30 Jan 2018, 19:21 last edited by
        #3

        I don't know about fancy. Right now I have 4 .pro files and a .pri file (with a script to select configuration). But I was able to add and modify (add files, etc) the existing project long after I added the initial .pro and .pri files.

        1 Reply Last reply
        0
        • M Offline
          M Offline
          mrjj
          Lifetime Qt Champion
          wrote on 30 Jan 2018, 20:27 last edited by
          #4

          Hmm, sounds pretty standard.
          Did you try to delete/rename the .user file and reselect compiler ?
          When its grey, have you check if it consumes CPU ?
          Im wondering if its possible to create some sort of circular structure and it
          simply never finishes.

          1 Reply Last reply
          1
          • R Offline
            R Offline
            Rlkcpo
            wrote on 30 Jan 2018, 20:56 last edited by
            #5

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

            I don't think its actually doing any work. All the processes seem to be running at idle. But at this point I don't want to rule out anything. It just seems highly unlikely that when using a managed make system (qMake) the IDE would ever block the ability of adding files to the project.

            M A 2 Replies Last reply 30 Jan 2018, 21:01
            0
            • R Rlkcpo
              30 Jan 2018, 20:56

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

              I don't think its actually doing any work. All the processes seem to be running at idle. But at this point I don't want to rule out anything. It just seems highly unlikely that when using a managed make system (qMake) the IDE would ever block the ability of adding files to the project.

              M Offline
              M Offline
              mrjj
              Lifetime Qt Champion
              wrote on 30 Jan 2018, 21:01 last edited by
              #6

              @Rlkcpo
              Ok. was just a thought.
              Yeah i cant think of a situation where it should stay locked.
              When its grey. It just stay grey for ever?
              What if you alter the .pro file from outside. does it prompt to reload?

              1 Reply Last reply
              0
              • R Offline
                R Offline
                Rlkcpo
                wrote on 30 Jan 2018, 21:07 last edited by
                #7

                Nope you were correct. It was the compiler. Not sure how or when it got changed but my kit deselected both the compilers associated with default kit (Desktop Qt 5.10.0 GCC 64bit). This caused the behavior I was seeing.

                1 Reply Last reply
                4
                • M Offline
                  M Offline
                  mrjj
                  Lifetime Qt Champion
                  wrote on 30 Jan 2018, 21:09 last edited by
                  #8

                  Super!
                  Good to know as its clearly not easy to spot.

                  1 Reply Last reply
                  1
                  • R Rlkcpo
                    30 Jan 2018, 20:56

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

                    I don't think its actually doing any work. All the processes seem to be running at idle. But at this point I don't want to rule out anything. It just seems highly unlikely that when using a managed make system (qMake) the IDE would ever block the ability of adding files to the project.

                    A Offline
                    A Offline
                    aha_1980
                    Lifetime Qt Champion
                    wrote on 30 Jan 2018, 21:15 last edited by
                    #9

                    @Rlkcpo

                    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.

                    Qt has to stay free or it will die.

                    M 1 Reply Last reply 30 Jan 2018, 21:32
                    3
                    • A aha_1980
                      30 Jan 2018, 21:15

                      @Rlkcpo

                      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.

                      M Offline
                      M Offline
                      mrjj
                      Lifetime Qt Champion
                      wrote on 30 Jan 2018, 21:32 last edited by
                      #10

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

                      1 Reply Last reply
                      2
                      • R Offline
                        R Offline
                        Rlkcpo
                        wrote on 31 Jan 2018, 12:35 last edited by
                        #11

                        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.)

                        M A 2 Replies Last reply 31 Jan 2018, 14:20
                        0
                        • R Rlkcpo
                          31 Jan 2018, 12:35

                          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.)

                          M Offline
                          M Offline
                          mrjj
                          Lifetime Qt Champion
                          wrote on 31 Jan 2018, 14:20 last edited by
                          #12

                          @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.

                          1 Reply Last reply
                          0
                          • R Offline
                            R Offline
                            Rlkcpo
                            wrote on 31 Jan 2018, 15:45 last edited by
                            #13

                            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.

                            1 Reply Last reply
                            0
                            • M Offline
                              M Offline
                              mrjj
                              Lifetime Qt Champion
                              wrote on 31 Jan 2018, 17:11 last edited by
                              #14

                              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 ?

                              R 1 Reply Last reply 1 Feb 2018, 12:09
                              1
                              • R Rlkcpo
                                31 Jan 2018, 12:35

                                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.)

                                A Offline
                                A Offline
                                aha_1980
                                Lifetime Qt Champion
                                wrote on 31 Jan 2018, 19:15 last edited by
                                #15

                                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.

                                Qt has to stay free or it will die.

                                1 Reply Last reply
                                0
                                • M mrjj
                                  31 Jan 2018, 17:11

                                  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 ?

                                  R Offline
                                  R Offline
                                  Rlkcpo
                                  wrote on 1 Feb 2018, 12:09 last edited by
                                  #16

                                  @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).

                                  1 Reply Last reply
                                  0
                                  • Y Offline
                                    Y Offline
                                    yugiquan
                                    wrote on 13 Feb 2023, 15:18 last edited by
                                    #17

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

                                    W 1 Reply Last reply 27 Jun 2023, 07:34
                                    0
                                    • Y yugiquan
                                      13 Feb 2023, 15:18

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

                                      W Offline
                                      W Offline
                                      weilu
                                      wrote on 27 Jun 2023, 07:34 last edited by
                                      #18

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

                                      1 Reply Last reply
                                      0

                                      • Login

                                      • Login or register to search.
                                      • First post
                                        Last post
                                      0
                                      • Categories
                                      • Recent
                                      • Tags
                                      • Popular
                                      • Users
                                      • Groups
                                      • Search
                                      • Get Qt Extensions
                                      • Unsolved