Rainer Clasen bea79092ab Fit: handle unknown fields gracefully
So far the FIT parser bailed out, whenever it found something
unknown/uninterested to GC. This is quite orthogonal to the FIT design, as
it's supposed to be extended.

renamed read_<foo> functions to match the FIT base_type names.

unified handling of "unavailable/invalid" values - i.e. if sensor data is
temporary unavailable. This allows easier and consistent handling -
especially for the uintXz base_types, which only differ by a different
"invalid" value. Had to change the type of the "values" list to int64 to
fit uint32/int32, as well.

added proper support for signed integer types. I'm wondering, why lon, lat
+ temperature were decoded properly...

added support for currently unsupported base types by just skipping their
bytes. This allows us to continue reading.
2011-07-23 13:57:49 +01:00
2009-10-03 17:57:22 -04:00
2010-07-27 19:46:35 +01:00
2011-07-23 13:57:49 +01:00
2009-09-20 11:13:11 -07:00
2009-09-20 11:13:11 -07:00
2006-09-06 23:59:42 +00:00

To build

  cp src/gcconfig.pri.in src/gcconfig.pri
  cp qwt/qwtconfig.pri.in qwt/qwtconfig.pri

Edit both src/gcconfig.pri and qwt/qwtconfig.pri as necessary, then

  qmake
  make

To uninstall the older FTDI VCP drivers on Mac OS X, open a Terminal and type:

  sudo mv /System/Library/Extensions/FTDIUSBSerialDriver.kext /tmp

Type your password when prompted, then restart your computer.
Languages
Standard ML 68.3%
C++ 28.1%
C 2.7%
Yacc 0.2%
QMake 0.2%
Other 0.1%