You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This issue would probably involve both GPSIO and sartopo:
Basically, it would be very nice to reduce the problem of trying to connect to the GPS before it is recognized by the OS, which results in one of a few different red line errors, in which case the user has to just try again after the device is fully recognized and mounted by the OS.
On windows, if javascript can recognize immediately that a new USB device has been plugged in, before it is identified or mounted, then it should be able to wait until the device is mounted as opposed to immediately returning a red line error.
If this is possible, the user could be shown something like "New device was just plugged in... waiting for it to be recognized..." with a counter (to show how long you have been waiting) and an abort button, and maybe an automatic timeout, with option to keep waiting, after some ridiculous period of time like 30 seconds... and there ARE GPSes that take more than 30 seconds to boot due to amount of data on the GPS.
The text was updated successfully, but these errors were encountered:
This issue would probably involve both GPSIO and sartopo:
Basically, it would be very nice to reduce the problem of trying to connect to the GPS before it is recognized by the OS, which results in one of a few different red line errors, in which case the user has to just try again after the device is fully recognized and mounted by the OS.
On windows, if javascript can recognize immediately that a new USB device has been plugged in, before it is identified or mounted, then it should be able to wait until the device is mounted as opposed to immediately returning a red line error.
If this is possible, the user could be shown something like "New device was just plugged in... waiting for it to be recognized..." with a counter (to show how long you have been waiting) and an abort button, and maybe an automatic timeout, with option to keep waiting, after some ridiculous period of time like 30 seconds... and there ARE GPSes that take more than 30 seconds to boot due to amount of data on the GPS.
The text was updated successfully, but these errors were encountered: