Menu
I have noticed that the library ActionBarSherlock display a lot of debug informations in my application, simply because there is a lot of lines like this:
if (BuildConfig.DEBUG)
Log.d(TAG, "[onCreatePanelMenu] featureId: " + featureId + ", menu: " + menu);
Fortunately, the log is displayed only on my debug device. Thanks to the if statement.
The big problem is that I would like to remove all the log on the debug device to focus on my code.
I know 2 solutions to avoid that:
Is there a simpler way to achieve this and to "fake" the library by telling it we are not on a debug device? I really would like to avoid the 2 above solutions.
777
The trick is, whenever there's a Debug.log it seems to open the log file, write something like 10 lines to it (call stack for the Debug.log), then close it. On certain devices (like iPhone) this is a slow process that can cause framerate issues, and I wouldn't be surprised if the file can get large enough to start affecting memory as well.
You can provide your own loggers using the debug API, and those loggers will still work when the player log is disabled. The player log is the output log that is generated automatically by Unity, and disabling it will probably not disable the rest of the Debug system (unless maybe they detect there are no available loggers).
If you have PowerShell 3.0+ dependent commands in your script, and you run it on a PowerShell 2.0 host, you will have errors in your compliance data that are not very easy to track down without enabling debug logging on the ConfigMgr client.
System debug logs are retained for 24 hours. Monitoring debug logs are retained for seven days. If you generate more than 1,000 MB of debug logs in a 15-minute window, your trace flags are disabled.
Open your ActionBarSherlock project
Open to the file /gen/com/actionbarsherlock/BuildConfig.java
And set DEBUG = false
191
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
