Reputation: 146940
I've got a Visual Studio 2010 C++ project. Previously everything was working fine but now when I create new files, they have strange little arrows in the corners. I've checked and they are not links, the files are at the hard location referenced. I've been through the project file and settings and cannot determine what on earth the difference is between them and my normal, good files. However, when I try to move these files to re-organize my project, Visual Studio won't move them. How can I solve this problem?
Here's (part of) the project file:
<ItemGroup>
<ClInclude Include="Interfaces\OS\OS.h" />
<ClInclude Include="Interfaces\Render\Math\colour.h" />
<ClInclude Include="Interfaces\Render\Math\Point.h" />
<ClInclude Include="Interfaces\Render\Math\rectangle.h" />
<ClInclude Include="Interfaces\Render\render.h" />
<ClInclude Include="Implementations\OS\Windows\Context.h" />
<ClInclude Include="Implementations\OS\Windows\Window.h" />
<ClInclude Include="Implementations\OS\Windows\Windows.h" />
<ClInclude Include="Implementations\Render\Direct3D9\Context.h" />
<ClInclude Include="Implementations\Render\Direct3D9\Direct3D9.h" />
<ClInclude Include="Implementations\Render\Direct3D9\Font.h" />
<ClInclude Include="Implementations\Render\Direct3D9\Label.h" />
<ClInclude Include="Implementations\Render\Direct3D9\Scene.h" />
<ClInclude Include="Implementations\Render\Direct3D9\Sprite.h" />
<ClInclude Include="Implementations\Render\Direct3D9\Texture.h" />
<ClInclude Include="UI\Context.h" />
<ClInclude Include="UI\Controls\Button.h" />
<ClInclude Include="UI\Controls\Context.h"/>
<ClInclude Include="UI\Division.h" />
</ItemGroup>
As you can see, all of the header files are listed equally, but only some of them are unmovable.
Upvotes: 1
Views: 211
Reputation: 146940
Apparently, this is something special. The problem only occurs if the root folder is named "UI". All other folder names work as expected. Re-creating the folder and files has no effect, but if the root folder is not named "UI", then everything correct. Going to chalk this one up to a Visual Studio error.
Upvotes: 5