-
Notifications
You must be signed in to change notification settings - Fork 121
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add command to create a .zip file with log.txt and groundcontrol.ini #717
Comments
isn't log.txt already in he user's home direcory?
|
|
That would be another way to address this. Opinions about having GC keep its .log file in the user's home directory? Would creating a folder within the user's home directory for the .log and .ini files be more 'polite' (I dislike programs strewing files about in my home directory)? |
What if there was a button which would ask them where they want to save the log and copy it to the location they specify? Kivy has a built in option for choosing where to save a file although I have not used it: https://kivy.org/docs/api-kivy.uix.filechooser.html |
That would do nicely. Navigating deep into 'the inner workings and midder mechanisms' of the GC app is off-putting for a user already battling an issue. If I understand, the suggestion is for grabbing a copy of the log rather than changing where the original resides, yes? |
I completely agree. Making this easier is a great way to help folks who are already dealing with an issue. I think making a copy would be better, but if it's much easier to grab the original I think that would be OK. We overwrite it every time the program launches so it would be no great loss |
One common request when helping to troubleshoot is for the user to post the groundcontrol.ini and log.txt files.
Adding a button that would gather those files into a .zip archive located in the user's home directory would make that step easier for the user.
Does this seem worthwhile? To avoid requiring the zipfile module, we could just make a copy of log.txt to the user's home directory and let them handle the compression...
The text was updated successfully, but these errors were encountered: