Trying to debug beaming in my application, I notice that the
ExgSocket.appData my application receives is all 0's, while I trace it
up to the ExgPut in the sending part, properly initialized:
SENDING
ExgSocketType socket;
typedef struct
{
UInt8 type;
UInt8 category;
Boolean exists;
UInt8 version;
} BeamInfo;
MemSet( &socket, sizeof( socket ), 0 );
...
BeamInfo *beamInfo = ( BeamInfo * ) &( socket.appData );
beamInfo->exists = false;
beamInfo->type = type;
beamInfo->category = dmUnfiledCategory;
beamInfo->version = AurigaCaveDBVersion; // = 39
error = ExgPut( &socket );
RECEIVING
ExgSocketPtr socket;
BeamInfo *beamInfo;
case sysAppLaunchCmdExgAskUser :
ExgAskParamPtr askParam;
askParam = ( ExgAskParamPtr ) cmdPBP;
socket = askParam->socketP;
beamInfo = ( BeamInfo * ) &( socket->appData );
beamInfo->version is now 0???
Is there a problem with this field? The typedef defines
UInt32 appData; // application specific info
What's wrong? Would it be a mis-documented pointer?
--
Luc Le Blanc
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palmos.com/dev/support/forums/
