GNOME Bugzilla – Bug 720809
read a float xml node return a bad value
Last modified: 2013-12-23 08:42:45 UTC
hi; when i read the ResultingFrameRateAbs node in Balser camera acA2500-14gm, i get value 0, but the right value is 14.59 at that time. so i use arv-evaluator-test with "0.06<>0?1/0.06:0"(this formal is simmilar to the way ResultingFrameRateAbs be caculated), the result is 0.
Hi. Thanks for the bug report. I think this bug is fixed in master since this commit: https://git.gnome.org/browse/aravis/commit/?id=bfee6bcd5f4cb46f94bcb333727ce652ebd890f2 Could you try to apply this patch to your installation. By the way, are you really using aravis on windows ? If so, we would be very interested on a feedback on what is needed for the compilation on windows, and what issues you probably had during the process. Cheers.
hi Emmanuel, i am not using on windows. i update the patch but still get value 0: $ ./arv-tool-0.4 control ResultingFrameRateAbs Basler-21317028 ResultingFrameRateAbs = 0 maybe i find where the bug is. if i modify the line 352 in arvevaluator.c: //if (length_double > length_int64) { if (length_double >= length_int64) { then get the right value: $ ./arv-tool-0.4 control ResultingFrameRateAbs Basler-21317028 ResultingFrameRateAbs = 14.5921 the change i think makes no efficiency because it treats all literal as float.
This commit should fix this issue: https://git.gnome.org/browse/aravis/commit/?id=cce7ef8b4ea7857a78817684a196ccb68241af2b
thanks, it works
Great. Thanks again.