You have to register your application with the EventGenerator in order to
be notified upon card insertion/removal. Please refer to the documentation
for the details.

OCF has it's own polling thread that creates the events, this thread will
call the cardInserted() and cardRemoved() methods of the EventListener you
have registered with the EventGenerator. Keep in mind that these methods
should return after short time to avoid tying up the polling thread.

Best regards,

Thomas

Thomas Schaeck
Pervasive Computing Division - Extended e-business Solutions, EMEA
Phone: +49-(0)7031-16-3479   Mobile: +49-(0)171-6928407   e-mail:
[EMAIL PROTECTED]   Fax: +49-(0)7031-16-4888
Address: IBM Deutschland Entwicklung GmbH, Schoenaicher Str. 220, 71032
Boeblingen, Germany


"Paul Sheridan" <[EMAIL PROTECTED]> on 20.03.2000 18:55:04

Please respond to "Paul Sheridan" <[EMAIL PROTECTED]>

To:   Thomas Schaeck/Germany/IBM@IBMDE
cc:
Subject:




Thanks this should help me a lot :)  On another point, any sample
applications I have seen that ship with the OCF1.2 release seem to allow
only one card insertion / removal etc.  What I want to do is write a small
test app which will respond indefinitely to cardInserted and cardRemoved
events until it is manually closed down by the user.  I have a class with
these functions as well as register/unregister and main...

Is this a threading issue ? do I have to spawn a new thread in the main()
function of the class  or how is it done ? and is this the same in a GUI
application ?

Thanks in advance,
Paul


_____________________________________

Get your free E-mail at http://www.ireland.com





---
> Visit the OpenCard web site at http://www.opencard.org/ for more
> information on OpenCard---binaries, source code, documents.
> This list is being archived at http://www.opencard.org/archive/opencard/

! To unsubscribe from the [EMAIL PROTECTED] mailing list send an email
! to
!                           [EMAIL PROTECTED]
! containing the word
!                           unsubscribe 
! in the body.

Reply via email to