Development environment to hack on RaceAnalyzer?

toga94m · Post by **toga94m** » Mon Dec 30, 2013 1:01 am

minijoe wrote:
brentp wrote:Can you post your sample log so we can check it out? Thanks!
I am using the sample logs from
http://dropcanvas.com/bthz0
Cheers,
Joe

Independently confirmed by two people (before I found this thread) over here - http://www.autosportlabs.org/viewtopic.php?t=4016 Seems to be dependent on logging rate of channels not being the same.

toga94m · Post by **toga94m** » Thu May 08, 2014 12:06 am

Would it be safe to use the latest wxWidgets 3.0.0 to attempt to build RaceAnalyzer, or should I stick with 2.9.4 as mentioned above?

Post by **brentp** » Thu May 08, 2014 12:35 am

2.9.4 would be the target you want, for certain.

toga94m · Post by **toga94m** » Fri May 09, 2014 2:12 am

Looks like GaugeWorks 1.1.0 has wxwidgets 2.6.2 hardcoded in the include paths... I changed it to point to my just-built 2.9.4, but am having troubles in GaugeWorks (most likely newbie troubles vs code troubles). Should I use wx 2.6.2 to build gaugeworks, then use 2.9.4 from that point on?

Post by **brentp** » Wed Jul 23, 2014 7:47 pm

Note, with the V2 firmware Race Analyzer will be retired and a new app - called simply "RaceCapture" will replace it. See more information here:
http://www.autosportlabs.com/racecaptur ... a-release/

Best thing is it's in a convenient and fast to develop python framework and will be cross-platform - Windows, Linux, OS X, iOS and android will ultimately be supported.