I like your suggestion though I will make it display minutes and seconds.
Although the log will definitely display seconds, it makes graphing easier.
Looks like we need to add some information to the packet for 1.3, this is for C and F in temperature mode. This means 1.3 for temperature range will require a firmware update.
I like your suggestion though I will make it display minutes and seconds.
Thank you. Also, if it rolls over 60 minutes it should be hours, minutes, seconds.QuoteAlthough the log will definitely display seconds, it makes graphing easier.
Agreed.QuoteLooks like we need to add some information to the packet for 1.3, this is for C and F in temperature mode. This means 1.3 for temperature range will require a firmware update.
But if the secondary display is showing "70.8F" can't you use that "F" to trigger the display of °F on the main display? And use "24.2c" to trigger °C?
Save saves the data shown on the plot, the established data is the plot data.
There needs to be an "About" or settings menu that includes the software version number. I am pretty sure that I woke up at 03:30 this morning after falling asleep watching a new Dave video and having some wine. (It was the late hour and wine not Dave, that did it of course...) and installed the new iOS test version, but I am not certain.
When I send data via email the subject line has the new Date_TIme subject line, but when I use "Save to Files" and use Box.com the file name it text.txt with no Date_Time at all. I think that "Save to Files" is going to be the method that I want to use so that name fix would be appreciated.
In limited testing it seems that the range (distance between phone and DMM) is better and so is recovery if the connection is lost and there is a re-connect.
Thanks!
Bug report:
On iPad, iOS 10.2.1, recorded some history to the graph, then hit Save, and the app crashed, dumping me back to the main iOS screen. It seems to do this all the time.
On iPad, iOS 10.2.1, recorded some history to the graph, then hit Save, and the app crashed, dumping me back to the main iOS screen. It seems to do this all the time.
Darn it yeah this was a suspicious for iOS 10... Error noted.
So in portrait, the save and other buttons are there. But, when I push save it kicks me out of the app (whether logging or not).
This is iOS 11.4 on an iPad mini 4.
On iPad, iOS 10.2.1, recorded some history to the graph, then hit Save, and the app crashed, dumping me back to the main iOS screen. It seems to do this all the time.
Darn it yeah this was a suspicious for iOS 10... Error noted.
I recall I am not the only one to see this problem. See below:So in portrait, the save and other buttons are there. But, when I push save it kicks me out of the app (whether logging or not).This is iOS 11.4 on an iPad mini 4.
Does it work on any specific devices you have?
Edit : This can happen when someone clicks Don't Allow when the permissions dialog appears. Not 100% sure thats the cause but it was for some other apps.
Does the TestFlight app send you crash reports?
Bug: Sometimes when pan and zooming on gragh, you get in a mode where the y axis labels and lines disappear and you can no longer see the data. No amount of pinching or dragging, or scrolling brings it back. Tapping reset doesn’t work either.
Build 1.3:
- Potential solution to iPad crashing when saving data
will add HH:MM:ss:mmm or something similar but that is a little to many characters for the graph we need something better.
Bug: Sometimes when pan and zooming on gragh, you get in a mode where the y axis labels and lines disappear and you can no longer see the data. No amount of pinching or dragging, or scrolling brings it back. Tapping reset doesn’t work either.
Did you try a double tap on the graph area? That should reset to the full auto-scaled view.
Quotewill add HH:MM:ss:mmm or something similar but that is a little to many characters for the graph we need something better.For the axis labels I don't think fractional seconds are needed. The time axis grid lines should be in round number intervals, so hh:mm:ss should be sufficient (it is only 8 characters and the colons are thin).
Quotewill add HH:MM:ss:mmm or something similar but that is a little to many characters for the graph we need something better.For the axis labels I don't think fractional seconds are needed. The time axis grid lines should be in round number intervals, so hh:mm:ss should be sufficient (it is only 8 characters and the colons are thin).
I agree. No need for fractional secomds.
The reasons that there are fractions of a second on the X axis are as follows:
- The range auto-scales to new data, new data arrives in fractions of a second
- If the range block auto scales (to the next round number) it expands in a jerky manner
- If I simply truncate the digits, preventing issue 2 then it is inaccurate
There are some things to try but I want to avoid block auto scaling as it is jerky. I also don't want to truncate as it is simply inaccurate.
I'm getting the frequency cut off in the display when viewing on a iPhone X (Thanks to the notch). Otherwise good so far. To be clear it is displaying, something, I just can't make out all of it.