passing callback_flag in async_api_setMessageCallBackOn function #9
Conversation
passing callback_flag in async_api_setMessageCallBackOn function
|
Many thanks for the contribution! let me add this to the next release, I still need to put together some new stuff already in the queue before releasing a new version but I've added to the development queue. Thanks! |
|
@user2684 I would highly appreciate if you could release the next version, i am stuck in a project because it requires this change. Thanks in advance. |
|
Hi, yeah sorry for waiting so long, I'm still trying to find out a reasonable default to the new Imou API limits which now is taking priority since preventing users to make all of this working. I should be ready by a couple of weeks max. Thanks for your patience! |
|
Hi, thanks for the timeline. It helps a lot .
Regards,
B M Abir
…On Sun, 2 Jun 2024, 21:41 user2684, ***@***.***> wrote:
Hi, yeah sorry for waiting so long, I'm still trying to find out a
reasonable default to the new Imou API limits which now is taking priority
since preventing users to make all of this working. I should be ready by a
couple of weeks max. Thanks for your patience!
—
Reply to this email directly, view it on GitHub
<#9 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABIYWSGUPN4LGJ472YULPITZFM4LXAVCNFSM6AAAAABGHNLTFSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCNBTHEYDKNZWGU>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
|
@user2684 Hi, Sorry for nagging you. But it has been a few months and this PR is still pending. Can you please look into it? |
|
Hi! Apologize, things slow down due to this |
passing
callback_flaginasync_api_setMessageCallBackOnfunction, as mentioned in this #8Its value is optional and has default value as before, thus backward compatible.