GOOP error 1031

[richjoh]

The Endevo generated class keeps reporting error code 1031 yet I know the connector pane matches the callee (a child class) connector pane. 

I'm using GOOP Inheritance toolkit, i.e. GOOP wizard 3.0, to add features to a working app. The GOOP wizard's Virtual VI (generated by the wizard) that I created or setup keeps showing an error 1031 "VI Reference type does not match VI connector pane" from the "Open VI Reference" function. This class is the virtual class and is used in the app to call the child class.

I am 100% sure the connector pane matches and the "dynamicCallMethod" VI on the block diagram and the VI reference on the front panel, yet the "Open VI Reference" spits out error 1031 error code. Wth

First time using GOOP, other classes I create work just fine... its only this issue...any hints would help.

[richjoh]

Apparently GOOP has a quirk. Its obvious the Caller's connector pane musts matched the callee's connector pane... Although the connecter panes matched, the "Open VI Ref" (on the block diagram) reported 1031 error. When I created both Class panes (connecter layout) I dragged its respective icons to the "vi reference" on the FP. This was fixed after I took the callee's (method) connector icon and drag it to the caller's " (virtual method) "VI reference".

How the error is reproduced I don't know... but I'de like to find out... Could this happen if I create the child class before the Virtual parent using GOOP???

Message Edited by richjoh on 11-04-2008 02:00 PM