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
What if all (post authentication) error handling/exceptions got sent to a new document that gets uploaded to the RM ? That way rather than dumping errors to the console or log file to possibly never be seen they would show up in the users' RMs?
This could also work as a notification method for feature changes so then functionality changes like this could get implemented with a default of "don't execute unless opt-in" and details are in the RM 'Goosepaper Update' document. Would still require a global config though.
The text was updated successfully, but these errors were encountered:
Interesting! One of my use-cases right now is to use Goosepaper to just generate a document, but not send it to a tablet. What would the analog be for that user? I definitely want to avoid logfiles cluttering up my own tablet but I could see other users benefitting from this! Definitely a long debug-cycle though (at least in my tests, the RM doesn't get the file all that quickly...)
LOVING these PRs and ideas, thank you @sedennial :)
So perhaps this could also be an option to go into the global prefs/config file? If we did that we could have multiple methods of logging as well. Log file, Syslog/Event Log, Upload logs to RM, etc.
Also I could see an option being 'Create a PDF/EPUB error log' and a separate check for uploading said debug/log document.
‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
On Monday, May 10th, 2021 at 7:22 PM, Jordan Matelsky ***@***.***> wrote:
Interesting! One of my use-cases right now is to use Goosepaper to just generate a document, but not send it to a tablet. What would the analog be for that user? I definitely want to avoid logfiles cluttering up my own tablet but I could see other users benefitting from this! Definitely a long debug-cycle though (at least in my tests, the RM doesn't get the file all that quickly...)
LOVING these PRs and ideas, thank you ***@***.***(https://github.com/sedennial) :)
—
You are receiving this because you were mentioned.
Reply to this email directly, [view it on GitHub](#45 (comment)), or [unsubscribe](https://github.com/notifications/unsubscribe-auth/AFK6AJCU6POQ47BVNX5YBF3TNCIFHANCNFSM44P7VQDA).
What if all (post authentication) error handling/exceptions got sent to a new document that gets uploaded to the RM ? That way rather than dumping errors to the console or log file to possibly never be seen they would show up in the users' RMs?
This could also work as a notification method for feature changes so then functionality changes like this could get implemented with a default of "don't execute unless opt-in" and details are in the RM 'Goosepaper Update' document. Would still require a global config though.
The text was updated successfully, but these errors were encountered: