Text version of the page

SOFTWARE PORTING INFORMATION

for the

CX100 / CX104 Frame Grabbers

Section 1

PORTING FROM THE FG LIBRARY TO THE CX LIBRARY
You need to read this section if you have Cortex I software that uses the FG libraries and youwish to port it to the CX100 using the CX libraries. This discussion also applies to our Windows DLL's. All libraries and DLL's are 16-bit.The FG libraries are our previous Cortex I libraries for the C programming language:FG_B.LIBBorland linkable library FG_M.LIBMicrosoft linkable library WFG.DLLMS-Windows Dynamic Link Library (DLL)The CX libraries are out new CX100 libraries for the C programming language:CX100_B.LIBBorland linkable library CX100_M.LIBMicrosoft linkable library CX100_W.LIBWatcom linkable library WCX.DLLMS-Windows Dynamic Link Library (DLL)If you are planning to use the CX100 as a Cortex I there is no need to port your code, since theCX100 operates as a drop-in replacement for the Cortex I. In fact, you should continue to use the FG libraries. The CX libraries initialize the CX100 in the CX100 mode and do not allow you to switch back to the Cortex mode.This section does not explain how to use the new features of the CX100 or the CX libraries. Itsimply shows you how to modify your Cortex program to make it link with the CX libraries. After you accomplish that, you can begin developing CX100 specific features. LIBRARY INITIALIZATION
Initialization is the most significant change between the FG and CX libraries. In the FG libraries,we recommended using find_fg(). You may also have used select_fg() or init_fg().find_fg() and init_fg() DO NOT exist in the CX libraries, and select_fg() has some significantdifferences.