Closed abdelaziz-mahdy closed 4 months ago
i dont think getLogTagLevel or stuff related to tags is needed, but will leave it since it may be needed in specific use cases that i dont know
also its test case fails, and i cant figure out the problem sadly
Actually I think it's not necessary to add async version, getting and setting log level are fast enough. In my test, allocate and free memories have extra cost that will damage the performance.
Actually I think it's not necessary to add async version, getting and setting log level are fast enough. In my test, allocate and free memories have extra cost that will damage the performance.
i thought that too, but i saw openCvVersionAsync so i followed it to match the sync async for all
Actually I think it's not necessary to add async version, getting and setting log level are fast enough. In my test, allocate and free memories have extra cost that will damage the performance.
i thought that too, but i saw openCvVersionAsync so i followed it to match the sync async for all
😂It's my fault too, async was somehow abused when we worked on it.
well well here i go will delete the async for logging and the version stuff
done, but i think test will fail again.
done, but i think test will fail again.
Ok, I will test and fix it.
@abdelaziz-mahdy I don't know why too, maybe the tag is not actually registered or available between different calls.
I searched in the repo of opencv and it seems the two API are not actually used. So, I think it's fine to remove setLogTagLevel and getLogTagLevel.
done, i think we can merge after ci is successful
@abdelaziz-mahdy Merged, thanks for your contribution!
implementing logging interface fixing https://github.com/rainyl/opencv_dart/issues/173
sync and async interfaces and test cases