Reloading our Activities State after firing Intent to camera

by Mark Murphy » Thu, 03 Sep 2009 10:15:45 GMT

Sponsored Links
 > Mark, so I'm confused.  No, the activity was not destroyed, but it

If the activity is not destroyed, there is nothing that needs saving --
the activity is still in memory.

Mark Murphy (a Commons Guy) 
Android App Developer Books: 


Other Threads

1. Permission at installation time and run tim

Yes it is the second one of course.

On Fri, Oct 23, 2009 at 2:56 AM, nguyenvuthiennga <

Dianne Hackborn
Android framework engineer

Note: please don't send private questions to me, as I don't have time to
provide private support, and so won't reply to such e-mails.  All such
questions should be posted on public forums, where I and others can see and
answer them.

2. GestureLibrary question/suggestion


I had my first dabble with the gesture library today. Two issues
reared their heads:

1) if I have a view that I'm not interested in scrolling, I still
can't have simple straight line gestures in both directions
(orientation has to be horizontal or vertical). Is there some way of
getting round this ?

2) Every developer defines their own gestures hard-coded to the
application functionality. One image program might use left-stroke for
'Previous Image' and another for 'Scroll Left'. It would be better IMO
to organize things like this:

 - applications publish *named actions*  (e.g. in manifest)  that
gestures can be hooked to ("Next Image", "Add Contact" etc)
   - there is a device-wide gesture library that the user can add
*named gestures* to with Gesture Builder ( "Straight Up", "Cup" etc)
and link the gesture to whatever actions are available
   - in onGesturePerformed, apps get passed only a string "Next Image"
or whatever and run the appropriate code

  - users can define gestures they like, to do what they like, in
whichever app they like.
  - the published actions could be linked centrally with other input
forms e.g. accelerometer gestures, voice command, hard button presses

OK, bit late maybe :-)


3. Web servers

4. Using external font in android application

5. Transfer Messages without Service Provider


7. arrays to be accessed by both JAVA n C thru JNI in an Android app