Revision history [back]
Thanks, that edit clarifies it. This happens if you store the project in a different directory than the ones you are adding, I think past a certain depth of '..'s to go back up (rather than displaying something like ../../../../develop/thirdparty/librealsense2. Is it possible to move the project so it's say in ~/develop? If so, doing Save Project As from the Project menu should solve it.
In general Wing tries to use relative path from project to files as the way to keep track of them so that if both the projects and files are moved but relative path stays the same then it can still find the files from the project. So there's some value of coupling project location to the location of the files in it.
Another thing to note: You don't need to add code you're using but not going to work on to the project, as long as Wing can find it through the Python Path. In general it's better to restrict what's in the project to files you'll actually want to search in the Search in Project scope or include in the Open from Project feature. Wing will still find the files for Find Uses, Goto Definition, Refactor, etc, as long as they are on the Python Path, and in fact it won't treat the project contents as Python Path, so adding them there won't cause Wing to resolve for example an import from librealsense2. I mention this just since it's in directory called 'thirdparty'; it may not be relevant to your use case.
Please let me know if this doesn't solve it for you. As far as I can tell there's no way right now to get the path to display differently in the case where Wing falls back to showing the full path to a directory in the Project tree, due to relative location of projects.
Thanks, that edit clarifies it. This happens if you store the project in a different directory than the ones you are adding, I think past a certain depth of '..'s to go back up (rather than displaying something like ../../../../develop/thirdparty/librealsense2. Is it possible to move the project so it's say in ~/develop? If so, doing Save Project As from the Project menu should solve it.
In general Wing tries to use relative path from project to files as the way to keep track of them so that if both the projects and files are moved but relative path stays the same then it can still find the files from the project. So there's some value of coupling project location to the location of the files in it.
Another thing to note: You don't need to add code you're using but not going to work on to the project, as long as Wing can find it through the Python Path. In general it's better to restrict what's in the project to files you'll actually want to search in the Search in Project scope or include in the Open from Project feature. Wing will still find the files for Find Uses, Goto Definition, Refactor, etc, as long as they are on the Python Path, and Path (and in fact it won't treat the project contents as Python Path, so adding them there won't cause Wing to resolve for example an import from librealsense2. I mention this just since it's in directory called 'thirdparty'; it may not be relevant to your use case.
Please let me know if this doesn't solve it for you. As far as I can tell there's no way right now to get the path to display differently in the case where Wing falls back to showing the full path to a directory in the Project tree, due to relative location of projects.