Greg,
I hope I didn't give you or anyone the impression that you had a list or that an actual list even exists. I was just hoping that since you are info-LabVIEW's 'insider' :-) you may be able to comment on how plausible, difficult or outlandish it would be to implement this idea from NI's Perspective.
My goal was to create a server that would hold state information and perform function calls that other (non-LabVIEW) programmers would be able to use in their own code. I happen to be a fan of ActiveX since it forces a type definition of passing parameters. Conventional DLLs are not explicit and must be supported by a lot more documentation. They also tend to crash hard when incorrect data types are mapped to them.
In any event, thank you for your comments.
Otto Dalmady
-------------------original message------------------------------------
Subject: Re: ActiveX server in Labview
From: "Greg McKaskle" <[EMAIL PROTECTED]>
Date: Mon, 17 May 2004 22:19:17 -0500
> I think we should include these enhancements in our LabVIEW wish list
> (hope you are listening Mr McKaskle). Perhaps NI developers can
> somehow tie activex into the event structure so a programmer can
> define events that correspond to activeX methods. Both the event and
> method would be created by the programmer. Also, allow for pointer to
> function capabilities for DLL callbacks.
>
Listening, but keep in mind that I'm not a secretary for the wish list
or anything.
As for hooking ActiveX events into the events structure, that was the
general idea in LV7, but ActiveX events are less asynchronous
notifications and more a function call with a funny calling convention.
So what is in LV7 is a subVI callback that you register.
Greg McKaskle
------------------End Original Message----------------------------------
CONFIDENTIALITY NOTICE: This e-mail transmission, and any documents, files or previous e-mail messages attached to it, may contain information that is confidential and/or legally privileged. If you are not the intended recipient, or a person responsible for delivering it to the intended recipient, please DO NOT disclose the contents to another person, store or copy the information in any medium, or use any of the information contained in or attached to this transmission for any purpose. If you have received this transmission in error, please immediately notify the sender by reply email or at mailto:[EMAIL PROTECTED], and destroy the original transmission and its attachments without reading or saving in any manner. (2)
