.. of point based editing, which is a bit difficult
without constraints like snap-to, guides, undo
or delete. But the basic concept is there to play
with.
.. of course it will still be possible to edit in a more
traditional 'blocks' and 'rectangles' way too but that
code hasn't been written yet.
.. compress and maths libs with win32 and gnu toolchain
.. WINKIT_INSTALL to specify where winkit is installed for MSVC toolchain
.. update gcconfig.pri to reflect this
.. initial code to display an ERG file for editing
.. this just introduces the basic model for rendering
the erg file and loading the model.
.. the interaction model using a 'points' editor will
follow next and then one to use 'blocks'.
.. There is a LONG way to go, this commit is just to
put a checkpoint down and test across platforms
.. most importantly start to remove any reference
to .lib or .a library files since these differ
depending upon toolchain.
.. instead we should use a combination of
LIBS += -Lfolder
LIBS += -llib
.. so for example
LIBS += ../qwt/lib/libqwt.a
becomes
LIBS += -L../qwt/lib -lqwt
and is now platform neutral.
.. this needs to be applied throughout to ensure
src.pro works for MSVC and GNU toolchains
.. it had become a bit of a mess with various changes
over the last 5 years so restructured into 3 sections
* core and platform config
* optional dependencies
* source and headers
This is to help make it easier to maintain, especially
since support for the MSVC toolchain is likely to mean
it is modified quite a bit (in section 2 anyway)
.. gets rid of an iritating compiler warning when
compiling with VS2015 and MSVC
.. is good because user metrics aren't fixed so the
assert assumption is wrong now
.. means we have to add assert.h to all the source
files that had it from including RideMetric.h
and want to use it.
... first set of syntax error fixes to compile GC using Visual Studio 2015
... changes are encapsulated and tested to not conflict with GCC compilation
Note: there is no full compatibility - so GC is not building with MSVC2015 yet
.. if you delete a user metric after adding it to the
interval metrics list the interval summary window
will crash.
.. the fix goes to source where the RideMetric::compute()
method now ignores metrics that are not known instead
of adding a NULL pointer to the results.
.. the DataFilterFunctions[] were not processed correctly
after validation of calls to named functions was added
and the correction applied previously only worked for
functions defined by the lexer/parser, not those defined
in DataFilterFunctions[]
.. this fixes that, but it would be nice if this was cleaned
up in to one unified place in the datafilter.
.. recent commit for Pmax on the PfPv plot introduced
a stray line of code settng cranklength incorrectly.
This results in the QA plot being blank and a warning
message from qDebug() about trying to read a cyclist
setting incorrectly.
.. logic error if/else for plotting rides vs dateranges
along with assumption that zones will not be NULL (esp
for running) lead to a repeated crash when running power zones
are not defined.
.. additionally, when summarising for a date range the table was
displayed for running vs cylcing based upon the current ride item.
This has been changed to use cycling power zones always.
.. the proper fix would be to summarize power time in zone for running
and cycling separately.
.. the compare logic appears to be unaware of power time in zone for
running and so does not have the same SEGV but will also need to
be updated to list time in zone for running and power separately.