(Dangerous) bug when PB IDE emulates paths
Posted: Sun Feb 11, 2007 5:28 pm
Hello!
I've opened a main file and several include-files; they're all saved, so PB emulates the path for those files correctly.
Now, I've opened a new tab to create and test a brand new procedure which has nothing to do with the other project. I left the new tab UNSAVED and created 5,000 new test-files (with a FOR-loop).
The PB IDE emulates a wrong path for this new tab: It takes the path from the saved project, but it should use the #PB_Compiler_Home-Directory.
Important note: I used a relative path:
This can be dangerous when testing Delete-Functions as I do currently. The saved project has nothing to do with the new tab in which I was testing new code.
I've opened a main file and several include-files; they're all saved, so PB emulates the path for those files correctly.
Now, I've opened a new tab to create and test a brand new procedure which has nothing to do with the other project. I left the new tab UNSAVED and created 5,000 new test-files (with a FOR-loop).
The PB IDE emulates a wrong path for this new tab: It takes the path from the saved project, but it should use the #PB_Compiler_Home-Directory.
Important note: I used a relative path:
Code: Select all
For n=1 To 5000
CreateFile(0, Str(n)+" ttttt.txt")
Next