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
It is unclear how to label something an enhancement request - perhaps the moderator does that.
It would be really helpful if the info that appears in the scroll window of the GCode Tab were also written to a file.
I would suggest a default name such as YYYY-MM-DD-HH-MM-txFX.log.
It can be helpful in reviewing what might have gone on, or to capture dumps (e.g. $$) for record or debug on the forum.
The text was updated successfully, but these errors were encountered:
If you have debug clicked in the tgFX pane then it writes all that out to
log.txt
On Mar 7, 2014 7:20 AM, "cmcgrath5035" [email protected] wrote:
It is unclear how to label something an enhancement request - perhaps the
moderator does that.
It would be really helpful if the info that appears in the scroll window
of the GCode Tab were also written to a file.
I would suggest a default name such as YYYY-MM-DD-HH-MM-txFX.log.
It can be helpful in reviewing what might have gone on, or to capture
dumps (e.g. $$) for record or debug on the forum.
Reply to this email directly or view it on GitHubhttps://github.com//issues/49
.
tgFX.jar build 3009
On linux I see three log files active; error.log, log.out and output.log.
All three are being used, but no sign of the results of $$ command to tinyG, which does appear in scroll window.
On Win7 , I don't see any log.txt file. Where is it in the file system?
It is unclear how to label something an enhancement request - perhaps the moderator does that.
It would be really helpful if the info that appears in the scroll window of the GCode Tab were also written to a file.
I would suggest a default name such as YYYY-MM-DD-HH-MM-txFX.log.
It can be helpful in reviewing what might have gone on, or to capture dumps (e.g. $$) for record or debug on the forum.
The text was updated successfully, but these errors were encountered: