Products > Test Equipment
121GW App Testing
<< < (7/38) > >>
JonM:
I have done some more testing and am seeing issues when my phone gets about 1.3 m away from the 121GW.  Moving it closer does not recover the connection. There could be some interference so I will do some tests in a clean environment later (outside in a park maybe). The phone is an iPhone 7 running iOS 11.4

I was going to test on my iPad Pro but TestFlight said that I used up my single allotted test copy. Maybe there is a setting to allow each tester to try it on multiple devices?

A screen capture will be sent via mail.
 
 
JonM:

--- Quote from: Seppy on June 12, 2018, 04:15:43 am ---
There isn't currently an option for that, I'll add it in, I don't want to do a full time stamp for each item though as it makes the data less importable.
I can however change the default filename to the following, how does that sound (it would also be the default email title):
"Log DD-MM-YY, HH-MM-ss.csv"

Edit: for sortablility the following format was selected, what do people think?
"YYMMDD, HHMMss Log.csv"

P.S. Post screenshots if possible we really need them for the App store submission.

--- End quote ---

How about

"YYYYMMDD-HHMMss-121GW.csv"

or

"121GW-YYYYMMDD-HHMMss.csv"

?

The '121GW-' prefix could be a setting in the app.

Us UNIXy guys don't appreciate spaces in filenames. I don't really see the need for commas either in this data. Space separated should be sufficient, in which case the suffix would be .txt or .dat or something.

It would be good to set the logging interval, and as someone else said, a "round number" for the time interval is nicer.

IanB:

--- Quote from: JonM on June 13, 2018, 12:53:41 am ---Us UNIXy guys don't appreciate spaces in filenames.
--- End quote ---

Windows FTW!  ;D

It's true though, spaces can cause grief in scripts and on the command line. I think underscore is more portable than dash, so that would give a name like YYMMDD_HHMMSS.csv


--- Quote ---I don't really see the need for commas either in this data. Space separated should be sufficient, in which case the suffix would be .txt or .dat or something.
--- End quote ---

Actually, comma separated with a .csv extension enables apps like Excel to open the file directly as a spreadsheet without any need for import filtering. So I would strongly favor retaining the current csv format and file type.
JonM:
I will never open the data in a spreadsheet but I can live with the commas, and maybe I even need them for the header. 98% of the time I will be using R and if there are spaces in the header without commas that will be a problem. In any case I will still have to cleanup the column names since they will become the column names in a R dataframe, and if spaces, and parens, in filenames  are an issue, they are far worse in variable names!

 
HKJ:

--- Quote from: IanB on June 13, 2018, 01:18:35 am ---Actually, comma separated with a .csv extension enables apps like Excel to open the file directly as a spreadsheet without any need for import filtering. So I would strongly favor retaining the current csv format and file type.

--- End quote ---

Only in part of the world, some countries uses "," as decimal separator and ";" between values in csv files.
Navigation
Message Index
Next page
Previous page
There was an error while thanking
Thanking...

Go to full version
Powered by SMFPacks Advanced Attachments Uploader Mod