-
Thank you Gordon for your reply.
So you mean basically just a column that is empty normally, and then could contain a value at some point?
What I'd like is a new row the instant an apps ask Recorder to do it. In my case when the user presses the button in the "stopwatch" app to get a lap time. The mentioned extra row is just for knowing if the row was taking automatically or my stopwatch app asked to take it.
If you're thinking about automatic lap times, I wonder if that is actually functionality that should be in exstats
My idea about the stopwatch app was to be just a frontend of Recorder, so you could just exit the app and launch it again later (or another frontend app) with the recording being made by Recorder. If I understand correctly Run is using exstats and Recorder is getting it's own data without it. Using or not exstats is something that I was thinking about, because it seems it has same features Recording doesn't (like average pace). But anyway exstats doesn't have features that I would like (like statistics per lap), and I'd like all that information to be analyzed in the smartphone or computer after downloading the activity. I was initially thinking about rewriting a widget from scratch, but Recorder does many of the things I need and I don't know much about Espruino and Bangle.js.
What you're seeing in the file you download from the recorder in app loader isn't quite what's saved to the device.
I wrongly assumed that the CVS was the raw data from Recorder. Good to know it's storing it more compact.
Allow saving both the internal HR sensor data and BT HR sensor data.
That happens automatically I think if you enable it in Recorder settings - BTHRM already has one of those recorder.js files
I thought that "Log HR" option was for saving HR data, and "Log BT HR" and "Log HR int" for choosing between them, my fault. Does exstats have the option to get the HR data from BT?
Someone asked if a run could be optionally paused/resumed, rather than just starting a new one each time. That should be pretty easy to implement in exstats
That was one of the things I wanted, but asking Recorder to create a new recording or appending to a previous one. I wasn't thinking about adding that functionality to exstats. I asked here about all of this to have some feedback from you guys that know much better about the current implementation.
You are reading a single comment by @adjtm and its replies.
Click here to read the full conversation.
adjtm
Yes, that sounds like a great idea.
So you mean basically just a column that is empty normally, and then could contain a value at some point? If so that would be easy to add as an extension. You can create a file
x.recorder.jsas part of your app which provides the extra column:https://github.com/espruino/BangleApps/blob/master/apps/recorder/widget.js#L146-L159
If you're thinking about automatic lap times, I wonder if that is actually functionality that should be in exstats, which is what actually provides all the stuff you see in the run app: https://github.com/espruino/BangleApps/blob/master/modules/exstats.js
What you're seeing in the file you download from the recorder in app loader isn't quite what's saved to the device. Time is saved at https://github.com/espruino/BangleApps/blob/master/apps/recorder/widget.js#L166 which is seconds since 1970. It's about 10 characters, so you could save some space by saving differences but it's probably not as worth it as you thought.
That happens automatically I think if you enable it in Recorder settings - BTHRM already has one of those recorder.js files: https://github.com/espruino/BangleApps/blob/master/apps/bthrm/recorder.js
Yes, it was just done because it was easy/reliable that way, but if you were willing to make it not reload then it'd be great.
Personally, there are some other features I think would be really good: