CALLback_cancel significance? | developer.brewmp.com CALLback_cancel significance? | developer.brewmp.com

Developer

CALLback_cancel significance?

Forums:

i am using ISMS feature and if i don't cancel the callback, the device/emulator crashes at the time of exiting application

is it must to call CALLback_cancel ?

vineet_sharma wrote:i am using ISMS feature and if i don't cancel the callback, the device/emulator crashes at the time of exiting application
is it must to call CALLback_cancel ?
Yes! If you have outstanding callbacks, you must cancel them before you exit the app. Otherwise they will be called anyway, after your app has exited and your module has (possibly) been unloaded.

vineet_sharma wrote:i am using ISMS feature and if i don't cancel the callback, the device/emulator crashes at the time of exiting application
is it must to call CALLback_cancel ?
Yes! If you have outstanding callbacks, you must cancel them before you exit the app. Otherwise they will be called anyway, after your app has exited and your module has (possibly) been unloaded.

Ben,
Is it required to cancel the callback even if the callback was fired?
Isn't it safe to assume that the system will not call the callback function again if it has called it once (unless you set a callback again)?
If yes, should I cancel the callback inside the callback function itself, ie, inside the function which the system will invoke?
Thanks for your help.

Ben,
Is it required to cancel the callback even if the callback was fired?
Isn't it safe to assume that the system will not call the callback function again if it has called it once (unless you set a callback again)?
If yes, should I cancel the callback inside the callback function itself, ie, inside the function which the system will invoke?
Thanks for your help.

If callback is fired, then it need to be cancel before exiting the application.

If callback is fired, then it need to be cancel before exiting the application.