Config.DEBUG is always false for the downloaded SDK so now I get it that this the value for the whole platform build (duh).
Config.DEBUG is not deprecated contrary to post from Dianne, although other fields in Config are deprecated starting in 1.6. For some reason it seems like you have read the source to find out what is deprecated since it is not shown in the API docs. On Oct 2, 1:16 pm, jotobjects <[email protected]> wrote: > I think you mean that each app should define some internal constant > and recompile for release (and not use the Config constants) ? Is that > right? > > Is there a conventional property or mechanism that the Log class uses > for isLoggable() method? > > The 1.6 release notes (API diff) says that all the Config constants > EXCEPT DEBUG are deprecated. The 1.6 javadoc does not indicate the > deprecation at all - so not clear how a developer would notice the > deprecation. > > On Oct 2, 12:35 pm, fadden <[email protected]> wrote: > > > On Oct 2, 12:14 pm,jotobjects<[email protected]> wrote: > > > > In 1.6 it is deprecated? > > > > What is the correct way to detect debug mode? > > > This is expected to be used as a compile-time constant within the app > > framework. You can and should build your app for "debug" or "release" > > as you see fit, independent of the state of the platform. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~----------~----~----~----~------~----~------~--~---
