I saw this issue again, -L and -I paths to sub folder not correctly updated
when saving upwards a directory level. But this time, I think I found a way to
make it repeatable. It seems that the symptoms do not show if I open the
project with the Open Project button. But, if I I open it by double-clicking
the .side file from Windows Explorer, then the symptoms do show.
A) What steps will reproduce the problem?
1. In Windows 7, Rename SimpleIDE/My Projects.
2. Copy My Projects from the attached zip to the SimpleIDE workspace.
3. USE WINDOWS EXPLORER TO NAVIGATE TO ...SimpleIDE\My Projects\Project Name\ AND DOUBLE CLICK Project Name.side TO MAKE SIMPLEIDE OPEN IT.
4. Verify that it builds correctly.
5. Click the Save Project As button.
6. Go up a directory level and save it as ...SimpleIDE\My Projects\Project Name (2).side
7. Build Project Name (2).side.
B) What is the expected behavior (output)?
Builds successfully because the 2nd and 3rd lines in the .side file are updated
as shown here:
Project Name (2).c
-I Project Name/library/libsimpletools
-L Project Name/library/libsimpletools
New File.c -> Project Name/New File.c
New File.h -> Project Name/New File.h
>compiler=C
...
C) What do you see instead?
Does not build successfully because the 2nd and 3rd lines in the .side file are
not updated as shown here:
Project Name (2).c
-I library/libsimpletools
-L library/libsimpletools
New File.c -> Project Name/New File.c
New File.h -> Project Name/New File.h
>compiler=C
...
D) Classify the bug as one of the following:
Somewhere between 1 and 2.
>>>1. Show Stopper<<<
>>>2. Medium Priority<<<
3. Cosmetic
4. Low Priority
E) Application Version and Platform:
Version
SimpleIDE 0-9-24
Platform
Choose OpSys from Labels Below:
OpSys-All, OpSys-Linux, OpSys-Mac, or >>>OpSys-Windows<<<
Specify Platform OS Version and 32 or 64 bit. For example:
Linux Debian (32 or 64 bit)
Linux Suse (32 or 64 bit)
Mac OSX (64 bit Lion)
Windows XP (32 bit)
>>> Windows 7<<< (32 or >>>64 bit<<<)
Provide any links or additional information below if possible.
Original issue reported on code.google.com by parallax...@gmail.com on 27 Apr 2013 at 3:14
Original issue reported on code.google.com by
parallax...@gmail.com
on 27 Apr 2013 at 3:14Attachments: