Welcome to the SR20 Community Forum - The Dash.
Register
SR20 forum logo

Thread: Feature Request - New Feature Log

+ Reply To Thread
Posts: 61-70 of 265
2012-09-19 04:02:36
#61
Originally Posted by JKTUNING

Not sure if I can do the lock windows, might be able to do a lock template which will lock everything.


That would be good enough, I sometimes resize sub windows by accident, or they get moved, then it's a pain to put them back.

Next Suggestion:
  • Combine Play/Pause button into one. While recording it should show as play button, while playing it should show up as pause, while paused it should show up as play.
I know that one might be hard, but it would open up some space for another button.

I've been pondering the idea of carputer, touch screen etc. Being able to adjust your tune from that would be just freaking awesome. Plus It would eliminate the need for physical gauges!
2012-09-19 04:12:41
#62
Ya pause an play in the same button would be good, that way it saves room.

Would it be possible to make it so people can set their own hot keys? I'd like to be able to hit space bar to start an stop recording, then another to save logs.

Or maybe I'm gettin to greedy heheh :P
2012-09-19 12:17:39
#63
Suggestion:
  • Parent the help window off the desktop, or maybe run it in a separate process, so it can be moved and sized separately from the main window.

Thanks,
Dave
2012-09-19 12:56:03
#64
Originally Posted by dfddfd2
Suggestion:
  • Parent the help window off the desktop, or maybe run it in a separate process, so it can be moved and sized separately from the main window.

Thanks,
Dave


I will look into this. Because of the nature of the application, it makes it tough to separate the window outside of the main MDI window.

Originally Posted by lynchfourtwenty
Would it be possible to make it so people can set their own hot keys? I'd like to be able to hit space bar to start an stop recording, then another to save logs.


I can definitely add custom hot keys, that isn't a bad idea.

Originally Posted by Vadim
.

Next Suggestion:
  • Combine Play/Pause button into one. While recording it should show as play button, while playing it should show up as pause, while paused it should show up as play.
I know that one might be hard, but it would open up some space for another button.


This is actually how it works already.. what you guys need to notice is that the "PLAY" button is actually the resume/stop LOGGING button and the "PAUSE" button is the resume/stop LOG PLAYBACK button.

So, no matter how I slice it, I would still need two buttons!
2012-09-19 13:20:51
#65
Originally Posted by dfddfd2
Suggestion:
  • Parent the help window off the desktop, or maybe run it in a separate process, so it can be moved and sized separately from the main window.

Thanks,
Dave


John what about having some .doc's or even .html files in the NismoTronic root directory, so that people can just surf it up. I think .html's would be best because of the links.

Originally Posted by JKTUNING

This is actually how it works already.. what you guys need to notice is that the "PLAY" button is actually the resume/stop LOGGING button and the "PAUSE" button is the resume/stop LOG PLAYBACK button.

So, no matter how I slice it, I would still need two buttons!


First I will add on to the complexity...
  • Ability to pause recording, then resume recoding right where it left off. Granted the triggers can help accomplish that, but only until you are trying to log everything (even outside of the trigger values).

What about redoing the structure of how the buttons work?

Brain dump:
Press Record button, log records, at that point the Play/Pause button shows up as Play, which if you press it it will stop recording and play the log from beginning. While playing Play/Pause button becomes Pause, while paused it is Play.

The Record button should be clickable at any point, incase you want to record right then (right now you have to uncheck play first). This is where having the log append to existing log would be nice too, otherwise you would overwrite the log if you clicked it by accident.

I'll look for some examples from how other software handles this though
2012-09-19 15:01:34
#66
Originally Posted by Vadim


John what about having some .doc's or even .html files in the NismoTronic root directory, so that people can just surf it up. I think .html's would be best because of the links.


They are already there in html format.. click on the index.html file and it should bring it right up in your brower!


First I will add on to the complexity...
  • Ability to pause recording, then resume recoding right where it left off. Granted the triggers can help accomplish that, but only until you are trying to log everything (even outside of the trigger values).

What about redoing the structure of how the buttons work?

Brain dump:
Press Record button, log records, at that point the Play/Pause button shows up as Play, which if you press it it will stop recording and play the log from beginning. While playing Play/Pause button becomes Pause, while paused it is Play.

The Record button should be clickable at any point, incase you want to record right then (right now you have to uncheck play first). This is where having the log append to existing log would be nice too, otherwise you would overwrite the log if you clicked it by accident.

I'll look for some examples from how other software handles this though


I am not going to redo the structures of how the buttons work as this is how I have been use to tuning, this is pretty much exactly how NepTune and most other softwares that have the graphing and logging all through the exe work.

I don't want to append to existing logs. I can make an "autosave" option that saves ALL of your logs via a time/date stamp in your LOGS folder though.

That way you don't loose any of your recorded data by accident (this would be an option in the settings).

Also, the reason you have to "uncheck play" is because this is what actually resumes the logging from the ECU.. with it in playback mode it is no longer logging from the ECU. It would fight what you are trying to playback if it did that!

Hondata handles it like this and it is clumsy to me, so that is why I designed it like this. It takes some getting use to, but all in all, is the easiest way to handle things.
Last edited by JKTUNING on 2012-09-19 at 15-02-00.
2012-09-19 15:08:29
#67
I figured it was the simplest way to program it in, but it definitely does require some getting used to, I'm fine with it now, but new people might be confusing.

Autosave would be nice, it could be useful when your doing multiple redline runs and want them saved as separate files for easier exporting to virtual dyno (since virtual dyno only likes one redline run per log). But the export to virtual dyno will take care of that too.
2012-09-19 15:20:39
#68
Originally Posted by Vadim
I figured it was the simplest way to program it in, but it definitely does require some getting used to, I'm fine with it now, but new people might be confusing.

Autosave would be nice, it could be useful when your doing multiple redline runs and want them saved as separate files for easier exporting to virtual dyno (since virtual dyno only likes one redline run per log). But the export to virtual dyno will take care of that too.


I will definitely add in the auto save for the logs when you are done recording, it will save them in your specified log folder in the settings section.
2012-09-19 21:39:01
#69
Originally Posted by JKTUNING
Originally Posted by Vadim
I figured it was the simplest way to program it in, but it definitely does require some getting used to, I'm fine with it now, but new people might be confusing.

Autosave would be nice, it could be useful when your doing multiple redline runs and want them saved as separate files for easier exporting to virtual dyno (since virtual dyno only likes one redline run per log). But the export to virtual dyno will take care of that too.


I will definitely add in the auto save for the logs when you are done recording, it will save them in your specified log folder in the settings section.


autosave with date is a super great idea, i was just out making a few logs and having to type the name sucks while driving, so i hit some random keys then enter lol

all these little features will help guys like me an vadim who do alot of our own tuning by letting us keep our eyes on the road an not the laptop lol
2012-09-19 21:59:04
#70
Setup the NEMU on-board logging, then just download the log(s) when you're done driving around collecting the data. Analyze the data, make your changes, clear the on-board log(s) and go again!

Dave
+ Reply To Thread
  • [Type to search users.]
  • Quick Reply
    Thread Information
    There are currently ? users browsing this thread. (? members & ? guests)
    StubUserName

    Back to top