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
Prompt the user to choose a location for storing the logfile when starting/stopping (TBD) the Logger
When starting/stopping (TBD) the Logger open an OS dialog prompting the user to enter a name and location to where saving the files, ideally the GoogleDrive will be mounted on the local PC, thus allowing to upload logs to Drive in an easy and transparent manner.
Notes
⚠ Even though it may lead to duplicated logs I would always keep the original location as a backup, in case some writes fail because of network connectivity, maybe something can be done to check if the location is a local resource and act accordingly. Anyhow in the early versions I would definitely keep both logs, one at a default location and the other one where the user pleases
Allow to select different log rates for different variables in order to not fill up local storage too quickly
ℹ I don't believe the following feature is worth implementing, however I will list it here ℹ
Using the ADJ specify a refresh rate for the variable when writing to disk
I don't think it is worth because in order to have variable rates you would have to have seleted an alternative location BEFOREHAND, this location might probably be a network resource with slow rw times so it may cause some trouble with the network card. Besides, I don't see a clear use case for this feature, if you can convince me otherwise definitely go ahead.
The text was updated successfully, but these errors were encountered:
Feature description
Prompt the user to choose a location for storing the logfile when starting/stopping (TBD) the Logger
When starting/stopping (TBD) the Logger open an OS dialog prompting the user to enter a name and location to where saving the files, ideally the GoogleDrive will be mounted on the local PC, thus allowing to upload logs to Drive in an easy and transparent manner.
Notes
⚠ Even though it may lead to duplicated logs I would always keep the original location as a backup, in case some writes fail because of network connectivity, maybe something can be done to check if the location is a local resource and act accordingly. Anyhow in the early versions I would definitely keep both logs, one at a default location and the other one where the user pleases
Allow to select different log rates for different variables in order to not fill up local storage too quickly
ℹ I don't believe the following feature is worth implementing, however I will list it here ℹ
Using the ADJ specify a refresh rate for the variable when writing to disk
I don't think it is worth because in order to have variable rates you would have to have seleted an alternative location BEFOREHAND, this location might probably be a network resource with slow rw times so it may cause some trouble with the network card. Besides, I don't see a clear use case for this feature, if you can convince me otherwise definitely go ahead.
The text was updated successfully, but these errors were encountered: