i have a better idea. i'm going to do something different for loading multiple logs, and stop this singular log buffer bullshit. its not doing any good.
i have a better idea. i'm going to do something different for loading multiple logs, and stop this singular log buffer bullshit. its not doing any good.
decided to drop the tabbed interface for the entire program and separate it into modules; it's totally outgrown a fixed-size tabbed interface, especially when i want to add a new feature.
this is a TON of work but in the long run it'll make it way easier to add new features without having to juggle the entire existing UI around.
there will be a small 'launch pad' window that launches each module
So now you're playing with dynamically created controls? That is a ton of work.
Why not just add a scroll bar to each tab? Or do like I do and get really fancy by putting panels that scroll on each tab so all the related stuff goes in a panel that scrolls.
nah nothing like thatSo now you're playing with dynamically created controls? That is a ton of work.
so the idea is to start treating eehack like a suite of separate programs (which it is) both as a coding paradigm and as a direction for the ui..
these programs can operated and developed independently, but share a common datastream and datalog. they'll be launched from one executable to avoid having to deal with IPC or whatever.
this looks a lot like the current design on the surface, but underneath is different.
there will be a module called 'launcher' which manages the connection status, and launches/manages the various other modules, configures the signalling between them, etc.
there's a module called 'datalog' which will be used to playback data, select/load/save logs, generally deal with incoming data dynamically, as in 'stuff you'd play back and scroll around in', but also the main dashboard. this module only listens, it doesn't command the ECM, but will select the available messages.
there's a module called 'controller' which does all the mode4 stuff, including autospark, actuator control, blm reset, etc.
another module for settings, etc... flash read write.. raw command interface..
the worst part is over. i've already got them seperated into qt 'widgets' so i can arrange them however i want (qt is really powerful that way). slashing up eehack to enable this level of compartmentalization and versatility took a massive diff worth 15,988 additions and 2,873 deletions. yet another thing i should have done from the ground up.
im still trying to decide how to manage the modules from a ui perspective.
tabs are alright, a singular tabbed interface inherently prevents simultaneous viewing and manipulating multiple modules, though.. no graphs beside your data..no mode4 by your dashboard.. etc. if i keep using tabs, it'll be mixed with separate windows.. large things in tabs, some small modules in separate windows where appropriate.
a small persistent launcher window with each module getting its own seperate window seems nice too, which is the model im testing right now, but relies completely on the user to maintain their own windows using...well... windows and its stupid taskbar. other than that, it's super flexible, and if a user just wants to use eehack as a flash tool, thats all they ever have to see.. nothing else gets in the way.
then there's the MDI (multiple document interface) design like tunerpro uses, a large container window. user still has to manage their own windows and prevent overlapping etc, but they're locked in a container, so you don't have your windows taskbar clogged up, and the entire thing can be moved around as a group, or scrolled overall...
it can live as seperate windows until i figure out how to contain the whole thing.
beta! http://fbodytech.com/download/223/
like i mention in the above post, the interface might not stay this way, i just want to prove that everything works properly when isolated.
but please do try it out and let me know how the threaded model works.. flashing.. etc
newest eehack beta freezes when opening for me, also runs up memory. uninstalled old eehack(single thread) then cleaned the registry then install the newest beta.
Attachment 10217
97z28 A4 obd1 swap(16188051)
Tunerpro Newbie
damn, i never did test it with windows 10
that'll give me something to do tonight.
it's a lot of code, i wonder what i broke?
oddly enough in this case the ui has loaded, which means everything else probably loaded too, but the version check hasn't succeeded yet. I've had problems with the qt network stupid thing crashing on load before.
unfortunately i just noticed i'd broken the 'auto-check update' flag in that beta.
here's a new beta just for you to try, and also a registry entry to disable update checking. can you try it, and if it doesn't work, use the registry entry to kill the auto-update, and let me know how that goes?
thanks for your help and testing as usual
http://fbodytech.com/files/eehack_tm..._jthompson.zip
copied eehack.exe over the existing and still freezing when starting, maybe a memory leak? when watching eehack load, in the task manager memory usage goes above 1000mb. also does the same with the auto-update reg used. Attachment 10218
97z28 A4 obd1 swap(16188051)
Tunerpro Newbie
it's strange; i can't reproduce that problem, and i can't think of anything that would loop and leak memory like that on startup. i'll dig into it a bit.
just for the hell of it can you go to my site and download a fresh copy, and install it libraries and all? i can't imagine i uploaded a corrupt version, but who knows? i tried it on two windows 10 machines and all is well..
completely uninstalled eehack and cleaned registry then rebooted. re downloaded and installed beta 4 from your site 10:20pm est usa. still wanting to freeze on startup but i can click on the modules and they will launch while its still trying to freeze up. as can be seen by the screenshots the mem usage going up
Attachment 10219Attachment 10220
97z28 A4 obd1 swap(16188051)
Tunerpro Newbie
so weird! i wonder what's different
i'll investigate further
This is actually pretty awesome that you've done this. I've thought about how great it would be to be able to create modules for eehack quite a few times. compiling now!
1994 LT1/4L60E Formula
compiled without errors. :)
couple of things, the analysis module's titlebar is named "form", and I can't select wideband for analysis. It's configured under settings and the data is there in the log.
1994 LT1/4L60E Formula
Posting Permissions
Reply With Quote
Bookmarks