forums.silverfrost.com

[Kenneth_Smith]

Thanks Paul, that�s useful. I almost got it right!

[DanRRight]

Two more small defects need fixing. They appear with no apparent reason, the attempts to make a demo extracting smaller snippets from the larger code reveals no errors in the code. Both causing program to crash instead of just stopping the code and asking how to proceed - ignore this problem and just do not execute the command or crash with the diagnostics message like many other Clearwin controls problems are currently being resolved

First is causing crash with "Too many %CA formats".

Another crashing with "To many line styles such as [style=0] used with [link=curves]".

Both these errors periodically kill a whole debugging day to find the reason and with %ca I could not find the solution for 20 years and in such cases just choose not to use %ca at all. The hint: this crash appears when many warning windows start to flood the screen, they appear for a split of a second and disappear by the next similar message which is made such a way that it also automatically closes previous window.

Same with any stiles, I just do not use any plot settings before calling %pl and rely instead on the settings in Designer's Mode. In some cases such preliminary settings together with Designers Mode are still desirable to use.

[PaulLaidler]

Dan

When you get into these kinds of coding failures I suggest

1) using /debug mode
2) when you get an error report, select the option to "quit with traceback" and then use the reported code line numbers in the traceback to locate the fault.

In extreme cases you could step one line at a time using the debugger.

I can understand that, if you repeatedly ignore error reports then eventually ClearWin+ will get lost in the confusion.

Don't forget to be careful with your use of ampersands to end each Window.

[DanRRight]

Paul,
That is exactly what my message was about. Of course I use /debug when revealing any error and doing that for 30+ years (3x longer than you guys at Silverfrost, as the fact that you have a debugger and it is the major golden compiler feature and selling point the Silverfrost and all its users "discovered" only when moved to 64bits a decade ago ) , the problem is that these two controls do not offer "quit with traceback" which i suggested to fix.

Right now the code simply crashes at %pl line in debugger with the complaint about too many styles (or about %ca with another case mentioned in previous message). The only I did not potentially do trying to understand your message correctly is that I have not tried the latest version of FTN95. May be you already fixed that. But I have to wait several days until my runs on my personal mini-super-compuPer finish. All 3-4 versions after 9.03 did not completely work with one of another of my code ( sometimes I was forced to use even 8.73 )

[PaulLaidler]

Dan

The option to continue after %ca and %pl errors has been provided for a number of years. If you are not seeing this option then the error dialog might be hidden behind another Window though this seems unlikely. Keep an eye on the taskbar when this happens.

Otherwise I don't have enough information to be able to work out what is going wrong for you.