Products > Test Equipment
121GW App Testing
<< < (15/38) > >>
Seppy:

--- Quote from: IanB on June 14, 2018, 02:49:33 pm ---
--- Quote from: Seppy on June 14, 2018, 02:38:17 pm ---That number is part of the X axis it is the left extreme of the visible values.
If that is the start of the plot that time represents the time between when mode was selected and when the first value was acquired. I might just zero it to avoid confusion.

--- End quote ---

Is it then 686.7 milliseconds? (See the picture attached to Reply #60 for context.)

--- End quote ---

Yes, 686.7 milliseconds  :)
IanB:

--- Quote from: Seppy on June 15, 2018, 01:35:56 am ---Yes, 686.7 milliseconds  :)

--- End quote ---

At other times I see time values like 0.307 k, which is a very unusual way to indicate time. I think it would be more friendly to format the time values like 5m07s. And I agree with resetting the left end of the time axis to zero.
Seppy:

--- Quote from: IanB on June 15, 2018, 01:41:51 am ---
--- Quote from: Seppy on June 15, 2018, 01:35:56 am ---Yes, 686.7 milliseconds  :)

--- End quote ---

At other times I see time values like 0.307 k, which is a very unusual way to indicate time. I think it would be more friendly to format the time values like 5m07s. And I agree with resetting the left end of the time axis to zero.

--- End quote ---

Its just standard SI notation, I like your suggestion though I will make it display minutes and seconds. Although the log will definitely display seconds, it makes graphing easier.

Progress Update:
- Device filter is now added to Build 1.3, tested and shown functional.
- 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.
rs20:
Just a pedantic usability thing, but I get confused when I see the "Save" button on a live feed of data. What am I saving? Do you actually mean "record"/"start logging"? It seems like the functionality here is very broadly similar to an audio recording application (only in the sense that new data is rolling in all the time, and the user wants to capture that data of a certain range of time). You never open an audio recording application to find a audio level indicator and just a "save" button. You record some data, and then save it; or possibly start recording to disk.

Whenever you see a "save" button, you already have a pre-existing well-established block of data (a document, a recorded audio segment, a PCB file) that saving simply instantaneously copies to disk/flash. If that's not what the button does, it shouldn't be labelled "Save".
Seppy:

--- Quote from: rs20 on June 15, 2018, 02:26:14 am ---Just a pedantic usability thing, but I get confused when I see the "Save" button on a live feed of data. What am I saving? Do you actually mean "record"/"start logging"? It seems like the functionality here is very broadly similar to an audio recording application (only in the sense that new data is rolling in all the time, and the user wants to capture that data of a certain range of time). You never open an audio recording application to find a audio level indicator and just a "save" button. You record some data, and then save it; or possibly start recording to disk.

Whenever you see a "save" button, you already have a pre-existing well-established block of data (a document, a recorded audio segment, a PCB file) that saving simply instantaneously copies to disk/flash. If that's not what the button does, it shouldn't be labelled "Save".

--- End quote ---

"Save" saves the data shown on the plot, the established data is the plot data.
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