Bulding Visual Clearwin Examples with VS2008

I really don't want to kill your nervs, but I was not very succesful on this task. (System Windows Vista Home Premium/VisualStudio Prof. 2008):

Solution 5 (Controls)

LINK : error - Attempt to call Void LinkText(Salford.VisualClearWin.Dialog ByRef, Byte*, Byte*, Int32) as if it were LinkText(Salford.VisualClearWin.Dialog*, Salford.Fortran.Character*, Salford.Fortran.Character*, System.Int32) caused by this Statements: CALL vcLinkText@(dlg1,'combo_Box1',comboText,80) CALL vcLinkText@(dlg1,'text_Box1',comboText,80)

Solution 9

LINK : error - Attempt to call Void ShowFiles(Salford.VisualClearWin.Dialog ByRef, Byte*, Byte*, Int32, Int32*) as if it were ShowFiles(Salford.VisualClearWin.Dialog*, Salford.Fortran.Character*, Salford.Fortran.Character*, System.Int32, System.Int32*)

Solution 10 (MDI)

Compiles and Links but crashes when I try to save the Textfile.

Solution 11 (SDI)

Compiles and Links but crashes when I try to save the Textfile.

Solution 15 (Tree)

When trying to save the tree:

System.Threading.ThreadStateException was unhandled Message: Für den aktuellen Thread muss der STA-Modus (Single Thread Apartment) festgelegt werden, bevor OLE-Aufrufe ausgeführt werden können. Stellen Sie sicher, dass die Hauptfunktion mit STAThreadAttribute gekennzeichnet ist. Diese Ausnahme wird nur ausgelöst, wenn ein Debugger mit dem Prozess verbunden ist.

caused by this Source Line:

CALL vcDisplayDialog@(dlg1)

Solution 16 (Paint)

Crashes on Save File.

Solution 17

Crash after start:

System.Reflection.TargetInvocationException was unhandled Message: Ein Aufrufziel hat einen Ausnahmefehler verursacht.

Solution 18

LINK : error - Attempt to call Void ShowFiles(Salford.VisualClearWin.Dialog ByRef, Byte*, Byte*, Int32, Int32*) as if it were ShowFiles(Salford.VisualClearWin.Dialog*, Salford.Fortran.Character*, Salford.Fortran.Character*, System.Int32, System.Int32*)

Solution 19

When trying to start:

System.Reflection.TargetInvocationException was unhandled Message: Ein Aufrufziel hat einen Ausnahmefehler verursacht.

Solution 20

Crashes on File Open System.Reflection.TargetInvocationException was unhandled Message: Ein Aufrufziel hat einen Ausnahmefehler verursacht.

Solution 21

When Trying to start:

Salford.VisualClearWin.Exception was unhandled Message: This form has more than one Tab_Control MDI container

Solution 22

LINK : error - Attempt to call Void LinkText(Salford.VisualClearWin.Dialog ByRef, Byte*, Byte*, Int32) as if it were LinkText(Salford.VisualClearWin.Dialog*, Salford.Fortran.Character*, Salford.Fortran.Character*, System.Int32) LINK : error - Attempt to call Void LinkGridText(Salford.VisualClearWin.Dialog ByRef, Byte*, Byte*, Byte*, Int32) as if it were LinkGridText(Salford.VisualClearWin.Dialog*, Salford.Fortran.Character*, Salford.Fortran.Character*, Salford.Fortran.Character*, System.Int32)

Solution 23

LINK : error - Attempt to call Void LinkGridText(Salford.VisualClearWin.Dialog ByRef, Byte*, Byte*, Byte*, Int32) as if it were LinkGridText(Salford.VisualClearWin.Dialog*, Salford.Fortran.Character*, Salford.Fortran.Character*, Salford.Fortran.Character*, System.Int32) LINK : error - Attempt to call Void LinkGridFont(Salford.VisualClearWin.Dialog ByRef, Byte*, Byte*, Byte*, Int32) as if it were LinkGridFont(Salford.VisualClearWin.Dialog*, Salford.Fortran.Character*, Salford.Fortran.Character*, Salford.Fortran.Character*, System.Int32)

Solution 5 (Controls)

LINK : error - Attempt to call Void LinkText(Salford.VisualClearWin.Dialog ByRef, Byte*, Byte*, Int32) as if it were LinkText(Salford.VisualClearWin.Dialog*, Salford.Fortran.Character*, Salford.Fortran.Character*, System.Int32) caused by this Statements: CALL vcLinkText@(dlg1,'combo_Box1',comboText,80) CALL vcLinkText@(dlg1,'text_Box1',comboText,80)

I confirm this error, running under Windows XP SP3 / Visual Studio Professional 2008.

It was also reported in the ClearWin+ forum under the subject 'Link Error for vcLinkText' in March 2007. There was an initial response 'I will see if I can run some tests on Monday' from Silverfrost, but the problem apparently wasn't resolved.

The description of the syntax is

SUBROUTINE vcLinkText@(dialog, controlName, text)
SUBROUTINE vcLinkTextEx@(dialog, controlName, text, refresh)
VCdialog dialog
STRING controlName
CHARACTER(LEN=*) text
INTEGER refresh

This indicates that the subroutine should have only 3 arguments, but changing the source code to

CALL vcLinkText@(dlg1,'combo_Box1',comboText)
CALL vcLinkText@(dlg1,'text_Box1',comboText)

causes compile warnings ‘warning 673: SUBROUTINE VCLINKTEXT@ has been called with too few arguments’, and the link error ‘Attempt to call Void LinkText(Salford.VisualClearWin.Dialog ByRef, Byte*, Byte*, Int32) as if it were LinkText(Salford.VisualClearWin.Dialog*, Salford.Fortran.Character*, Salford.Fortran.Character*)’.

I can see the problem and will aim to fix it as soon as I can.

This turns out to be a long standing regression in DBK_LINK that has now been fixed for the next release (coming soon).