On Thu, Jul 31, 2008 at 8:59 PM, Jeff Loucks <[EMAIL PROTECTED]> wrote:
> Except that notifyDetailsP isn't a pointer in this case. It is the > value itself. Do the following: > > UInt16 device = (UInt16)(((SysNotifyParamType*)cmdPBP)->notifyDetailsP); > > If you have any question about the use of notifyDetailsP, display the > value of notifyDetailsP from the notification handler and see if it is > a pointer, or the value itself. I found it to be the actual value, not > a pointer to the value. Ok, that looks good. I never really understood much about pointers and casts... :-( So, IF that works, then I still have the 'problem' of two notifications. I haven't found this to be the case yet, but maybe they are being missed. The problem I see here would be that the first notification may be the power, thus getting ignored. The second may be the serial/usb, and may get missed... ? Also, I don't exactly know what to do with the hex (?) values. Can I just if (device == 0x0010) or should I convert it to decimal somehow? Or is it dec? Sorry for my total ignorance... Well, I'll see what happens.. Thanks a lot! -- Christopher Stamper Email: [EMAIL PROTECTED] Web: http://tinyurl.com/2ooncg gTalk: http://tinyurl.com/6e359r Skype: cdstamper -- For information on using the ACCESS Developer Forums, or to unsubscribe, please see http://www.access-company.com/developers/forums/
