Bob wrote: > While I have only had the demo version of DeltaCad for a few days, I > have some observations. Perhaps others can provide > more.
I have observed these problems with DeltaCad. Regards, Steve 1) If your PC graphics mode is 1280x1024 or greater, the functions for text editing misbehave. Multiple spurious error messages are generated which the user has to click on before processing can continue. This is the worst problem I know of, as I encounter it frequently. Once past the spurious errors, the text edit box can be used and processing normally continues. 2) However, if the chosen action is to alter the justification of the text, the application loops and then crashes. 3) Splines must not have more than 248 points, and irregular polygons (shapes) are limited to 748 points. If more points are used, either or both of the application menu and the drawing will be corrupted. There is no error message on the call to dcCreateSpline and no warning in the manual that these limits exist. I only found out about it after sending their tech. support a failing programme. I was making splines with 365 points when I hit the problem. The limit is a trap for the unwary, but since drawings are not noticably degraded by omitting every second day, it is simply a matter of using only 183 points in a curve. I moved over to using splines because the drawing is generated much faster than when multiple straight line elements are used. 4) The Basic interpreter intermittently reports spurious syntax errors if there are a series of subroutine calls one after another, where the subroutine takes more than one parameter and the parameters values supplied are constants e.g. ... do_sub(1,2) do_sub(3,4) 'an error is reported for this line. do_sub(5,6) ... Sub do_sub(ByVal param1, ByVal param2) ... End Sub It seems to go away if you use the Call keyword: Call do_sub(1,2) Call do_sub(3,4) Call do_sub(5,6) ....
