I tend to do what TreKing suggested. I have a class called CommonVariables that really holds static strings for Flurry event names, the year parameter for my app (it's seasonal and changes once a year) which is used all over the place, and things like that.
-- Chris Stewart http://chriswstewart.com On Wed, Mar 9, 2011 at 3:53 PM, TreKing <[email protected]> wrote: > On Wed, Mar 9, 2011 at 2:41 PM, David Williams < > [email protected]> wrote: > >> What is the best way of going about setting up global variables? > > > IDK about "best", but "easy": public static values somewhere that you set > up in a custom Application class. > > > ------------------------------------------------------------------------------------------------- > TreKing <http://sites.google.com/site/rezmobileapps/treking> - Chicago > transit tracking app for Android-powered devices > > > -- > 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 > -- 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
