This makes more sense to me. I'd still argue for just one hash, probably md5 because it's shorter and md5 tools are common. Since there's no copy/paste, anyone who uses this will probably not actually be comparing every digit, never mind 3 different hashes.
Should also consider how it behaves on large files, e.g. if someone does properties on a DNG or video file, does the camera become unresponsive for a very long time or crash?
As it is now, most of the information is available directly in the file browser, although being able to see seconds in the timestamp and the exact size does have some value. File attributes could also be included.
#include <stdarg.h>static int fs_sprintf(int calc_hashes, char* str, const char* format, ...){ int i, index = 0; va_list argptr; if (calc_hashes) for (i = 0; i < 8; i++) str[index++] = ' '; va_start(argptr, format); index += vsprintf(&str[index], format, argptr); va_end(argptr); return index;}
warning: implicit declaration of function 'vsprintf' [-Wimplicit-function-declaration] index += vsprintf(&str[index], format, argptr);
(.data+0x8ec): undefined reference to `vsprintf'
long vsprintf(char *s, const char *st, __builtin_va_list va){ return _vsprintf(s, st, va);}
Question: why is this required?
Because wrappers are required to ensure clean arm/thumb transitions (on pre-digic 6 cameras) and we didn't previously need one for vsprintf itself.
Started by m2tk « 1 2 » General Discussion and Assistance
Started by sleepydog « 1 2 » Hello, I'm a NEWBIE - HELP!! (Newbies assistance, User Guides and thank you notes)
Started by dizzy314 Feature Requests
Started by wj906 Hello, I'm a NEWBIE - HELP!! (Newbies assistance, User Guides and thank you notes)
Started by waterwingz « 1 2 ... 10 11 » General Discussion and Assistance
