Closed daniel214 closed 2 years ago
Oops, meant "skip-checks: true" on that last one! 😬
For adding better debug output only adding an external dependency feels a bit overkill... :) but this feature might have some other uses as well, like the config file parameter you already had started or specifying a device in case there's multiple M8s connected etc.
This seems to break Windows builds currently, would probably need the relevant library package added there as well and the .dll file added to the output zip before this can be merged. I can try to add them/test the Win build at some point, not sure yet when exactly...
Yes, I agree, but as you said there are a lot of possibilities to make things quite a bit easier. My intention with splitting off the logs is so that you can easily tackle things like #51 by adding a few more debug lines and calling with --log-input=verbose
. It could also assist with graphics issues using --log-render=debug
which now prints driver info and enables the fps log message.
When I selected argp, I didn't realize it is almost completely unsupported in windows. I think there are really easy ways to do it, but I'm also wary of statically linking a GPL library.
Thanks for the PR. Unfortunately I don't think I want to add another dependency for now, especially something that might cause cross-platform problems. Those users who need deeper debug messages probably are capable of uncommenting the relevant define in code or passing the compile time flag. This method could be a good possibility though at some point if more advanced command line parsing is needed.
This PR
Known Issues
-?
flag does not work because it interacts with zshSample output: