I was wondering if anybody out there ran into an issue in regards to not being able to run a testcase after the all code was compiled. I think there might be an issue in which Silk will not report compile errors if there are any. This gives the illusion that your code is error free when it is not.
<BLOCKQUOTE><font size="1" face="Verdana, Arial, Helvetica">quote:</font><HR>Originally posted by KS: It is my assumption that this bug is being reported. If not, you might want to report it so it can be fixed in 6.0. <HR></BLOCKQUOTE>
I reported it several weeks ago and recently received confirmation from Segue that it is fixed in 6.0.
Also, to recover from this behavior pull down the Run menu and select Compile All. It'll then run normally (for .T based runs anyway, .pln runs are quite a bit more persnickety.)
Sometimes I have to run a compile on any modifed included files I am working on in order to see the errors in that, then once I've fixed those I can 'compile all' then run.
Test.t compiles (all) with no complaints, but won't run. It uses "app4.inc", which I have open and am editing. Running a compile on it will give an error, which is why test.t wouldn't run. Fixing that error then running test.t fixes the problem.
Can't wait for 6.0 to fix this bug that I run up against every day.