new $EE tuning thing!

[fbody_Brian]

Awesome!
I compiled it against the 5.6 beta release located here:
http://download.qt.io/development_re....6/5.6.0-beta/

[fbody_Brian]

and let me just state how fantastic it is to have this as a native binary running on linux!
Really stoked about that.

[steveo]

and let me just state how fantastic it is to have this as a native binary running on linux!
Really stoked about that.

me too.. it wasn't really an official goal, just a side effect.

it's too bad it requires bleeding edge QT to run, though, that screws us out of distribution packages for probably a year. hell, most distributions still run QT4.x

being GPL i could technically just copy qserialport into my source tree, rename the class, and then the serial driver is part of eehack's distribution, but i'd like to avoid that.

Next test.... flashing.

if datalogging and tweaking parameters works without generating errors, it should be alright.

[fbody_Brian]

an observation
when loading multiple log files (appending) if you have already selected items in the graph view they do not update or append the view until you select a different item in that graph. Once you select a new item then the graph extends to include the appended data.

here, the bottom graph shows the whole datalog, whereas the upper graph still shows the previously loaded data.
Attachment 10068

any way to have it replot on loading or appending a log file?
Edit:
Should I be submitting these things as requests/bug reports to github? or is it ok to post in this thread?

[steveo]

when loading multiple log files (appending) if you have already selected items in the graph view they do not update or append the view until you select a different item in that graph

as it stands right now, i expect when new data is added, that the user click the re-plot button themselves to update the graphs.

here, the bottom graph shows the whole datalog, whereas the upper graph still shows the previously loaded data.

having the two graphs out-of-sync due to selecting new data in one graph is certainly a case i didn't think of. i'll likely have to make it refresh BOTH graphs when selecting new data. this isn't a large amount of overhead, as plotting is very fast.

any way to have it replot on loading or appending a log file?

i'd rather force the user to do that manually, otherwise, do i draw the line just at loading a log? what about recording new data?

i originally planned to have to manually refresh all the time, but updating the graphs when selecting data sets was just too useful to pass up.

i want to avoid graphing causing any unintended overhead in the rest of the program. if a user selects a graph item, then goes to load a new log, should he really have to wait extra time for the graph to update?

perhaps i should simply clear the graph when loading new log data or recording new data, but i'd rather leave it plotted as-is

[fbody_Brian]

perhaps i should simply clear the graph when loading new log data or recording new data,

This gets my vote.

As it is now, you can clear the logged data and load a new log yet the graph still shows the previous logs data. If the user is aware of the behavior it's really not a big deal though. it's simple enough to click the replot button.

[steveo]

go grab fresh source from git, i think i fixed the graphing behavior.

it uses a simple 'data stale' state flag, and works on the assumption that data can't be loaded while the graph tab is active, and switching to the graph tab is only done when graphs are desired

it also actually 'clears' the graph when there's no data (before it just bailed if there was no data)

see if you can break it