Fixed a major bug that caused flow view to be totally broken.

This commit is contained in:
Collin Kidder
2015-08-19 19:56:22 -04:00
parent 23306832ae
commit 32c38e2331
3 changed files with 2 additions and 11 deletions
+1 -1
View File
@@ -1,7 +1,7 @@
#ifndef CONFIG #ifndef CONFIG
#define CONFIG #define CONFIG
#define VERSION 134 #define VERSION 135
//try to keep this in sync. //try to keep this in sync.
//SavvyCAN will complain if you connect a GVRET board with a revision //SavvyCAN will complain if you connect a GVRET board with a revision
+1 -1
View File
@@ -324,7 +324,7 @@ void FlowViewWindow::refreshIDList()
if (!foundID.contains(id)) if (!foundID.contains(id))
{ {
foundID.append(id); foundID.append(id);
//QListWidgetItem* item = new QListWidgetItem(Utility::formatNumber(id), ui->listFrameID); QListWidgetItem* item = new QListWidgetItem(Utility::formatNumber(id), ui->listFrameID);
} }
} }
//default is to sort in ascending order //default is to sort in ascending order
-9
View File
@@ -9,19 +9,10 @@
#include "serialworker.h" #include "serialworker.h"
/* /*
This first order of business is to attempt to gain feature parity (roughly) with GVRET-PC so that this
can replace it as a cross platform solution.
Here are things yet to do
- Ability to use programmatic frame sending interface (only I use it and it's complicated but helpful)
Things that were planned for the GVRET-PC project but never completed. Things that were planned for the GVRET-PC project but never completed.
Single / Multi state - The goal is to find bits that change based on toggles or discrete state items (shifters, etc) Single / Multi state - The goal is to find bits that change based on toggles or discrete state items (shifters, etc)
Range state - Find things that range like accelerator pedal inputs, road speed, tach, etc Range state - Find things that range like accelerator pedal inputs, road speed, tach, etc
fuzzy scope - Try to find potential places where a given value might be stored - offer guesses and the program tries to find candidates for you fuzzy scope - Try to find potential places where a given value might be stored - offer guesses and the program tries to find candidates for you
Things currently broken or in need of attention: (push these over to github issues as soon as you can)
*/ */
QString MainWindow::loadedFileName = ""; QString MainWindow::loadedFileName = "";