Call problems in VPE6.0 (Progress)

[therese]

Hello,
We have upgraded from VPE 3.50 to VPE 6.0.

After that I get an error in the log saying:
'VpeSetPen pro/make_vk_bag.p' Line:0) 'C' Call Stack has been compromised after calling _VpeSetPen@16 in vpep3260.dll (6069)

Code included:

/* void VpeSetPen(long hDoc, int pen_size, int pen_style, COLORREF color); */
procedure VpeSetPen external {&VPEDLL} PERSISTENT.
define input parameter hDoc as long.
define input parameter pen_size as long.
define input parameter pen_style as long.
define input parameter acolor as long.
end procedure.


Call:
define variable hdoc as integer no-undo.
run VpeSetPen(input hdoc,0,0,0).

This happens when I call VpeWrite too, so it seems to be an overall problem.

Any suggestions???

[IDEAL Software Support]

The parameter PenSize is now of type double. Check the updated documentation, many parameters have been changed to type double on the transition from VPE v3.x to VPE v4.0 and higher.

[therese]

OK, I notised that after a while. It's a BIG / HUGE problem that Ideal keeps changing existing functions when releasing new versions. It's making the upgrades very costly and time consuming when we no longer can use our old code...

[IDEAL Software Support]

The v3.x API was stable and fully backwards compatible for about 10 years. With v4.x in 2007 we changed the API once and since then it is backwards compatible. I don't know what you mean by saying "Ideal keeps changing existing functions when releasing new versions". This is simply not true.

Furthermore the change of the data type only requires a recompilation of existing source code - at least with most programming languages.