Documentation Roadmap

DescriptionSection
Generic Device Access
General ePad AccessGeneric ePad Access
Main ePad EnumeratorIIEPadEnum
Supplement ePad AcessgIEDebugGUI
Generic Pad InformationIIEEPADINFO
Generic Pad EEPROMIIEEEPROM
Generic ActiveX AccessGeneric ePad OCX Control
ePadInk
ActiveX ControlEpadInkLib::_DEpadInk
Main InterfaceIWedge
GraphicsText/Graphics on ePadInk
Low-levelePadInk - USB level protocol, usb_io.h
SamplesePadInk - Sample files
Internal ArchitectureinkUSB Internal Architecture
ePadId
ActiveX ControlePadLib::_DePad
Main InterfaceIePadIDFSR
ePad II
Main InterfaceIEPadXV
Other InterfacesIIEEEPROM, IIEEPADINFO
ePadId Pro
Main InterfaceIePadPro
Other InterfacesIIEEEPROM, IIEEPADINFO
Coding RuleePadPro Coding Rules
ePadInk Pro
Main InterfaceIePadPro
Other InterfacesIIEEEPROM, IIEEPADINFO
SamplesePadInkPro - Sample files
Coding RuleePadPro Coding Rules
ePad LS
Main InterfaceIePadLS
Widget InterfaceIePadLSWidget
Widget EventsePadHancockLib::_IWidgetEvents
Other InterfacesIIEEEPROM, IIEEPADINFO
ActiveX ControlePadLSActiveXLib::_DePadLSActiveX
Programmer NotesePadLS_Programmer_Notes
SamplesePadLS - Sample files
Client/ServerSupport Matrix for Citrix / Remote Desktop
Pad DetectionDetermining Pad type via Class Id

Each hardware device will have it's own "Service Provider." Make sure to check each service provider's documentation for additional options that may be available via the gIEDebugGUI interface.


Generated on Mon Dec 17 17:19:29 2007 for ePadAPIs by  doxygen 1.5.4