sprintf()

hi,
how to convince sprintf func to print "3,23 RAD" from long l = 3234?

sprintf(osd_buf, "%ld,%02ld RAD", v/1000, v%1000); prints "3,234 RAD"

can we use floats in sprinf?
thx.

sprintf(osd_buf, "%ld,%ld RAD", v/1000, v%1000/10);
or
sprintf(osd_buf, "%ld,%ld RAD", v/1000, v/10%100);

can we use floats in sprinf?

Yes, but it is not recommended to use floating point operations, because they are emulated (CPU does not have FP-coprocessor).

And since nobody asked: yes, I too think it would be better if the battery voltage reading was 2,43V instead of 2,432

And since nobody asked: yes, I too think it would be better if the battery voltage reading was 2,43V instead of 2,432

yes, i'm going to leave only 2,34 but that's not only for that

Deleted

as i can see, those measures are not ideal, discharge is not linear and batteries also vary between changings so i don't think you can relay on them. think 2 digit fraction precision is right in place if not too precise...

but don't worry i'm not going to put it into trunk, though it is only changing 3 numbers in source code
i'm thinking about sth else with that sprintf()...

I only keep the voltage on display, no icon to waste space. Any percentages the software can calculate can be rude guesses at best and that goes for the icon as well. Battery voltage varies primary with load as much as with capacity. I'm pretty familiar with how batteries behave so for me the voltage is way more clear indicator than an icon or percentage...

That's why I'd like the SI unit "V" letter there, to keep my brain clear that this is the battery voltage and not a part of DoF or anything else. And to put in that extra letter, one digit should be removed to prevent clutter... When a feature really does something for battery load, the voltage sinks significantly at least fast for my camera. The voltage measurement obviously isn't accurate to 4 digits either but that's not an issue here as absolute voltages aren't important, changes are and they are supposedly fairly accurate unless the last digit is all noise.

Moreover, I'd be thrilled if someone found a way to disable Canon's own low battery icon blink. It messes up my precious CHDK displays when it appears and is actually doing this half the time as it seems to be tuned for alkaline batteries instead of the (Eneloop) NiMH cells I use.

But I really don't feel strongly about this, I can perfectly well patch me a build for myself if people think the last digit is important. Maybe it is for cameras with lithium battery packs.

by the way, can the v value be used for some kind of benchmarks?
my s3is shuts down on about 4230 left. does this value depend on something? is it camera dependent? what values work for your s3is, barney? sorry this partly being offtopic.

by the way, can the v value be used for some kind of benchmarks?
my s3is shuts down on about 4230 left. does this value depend on something? is it camera dependent? what values work for your s3is, barney? sorry this partly being offtopic.

It's definitely camera model dependent since the battery voltages are highly different for different technologies. Mine shuts down at about 2,0 V I suppose, but it's easy to be mistaken and think it's 2,2 V because using playback mode on empty batteries will give me more than a 2,2 V reading and the camera may shut down instantly if I do the battery-hogging switch to rec mode.

for my s5 it is also sth like 4250mV..

btw sprintf(): i have modified a little file browser with minor changes (filesize in b,kb,mb,gb, selected filesize sum, trunk long paths, 10 rows and some fixes to gui)
if you want to try...

edit: added patch file