Passing parameters to new Activity

by vincent.gann...@gmail.com » Tue, 03 Mar 2009 02:52:03 GMT


Sponsored Links
 Hi all,

I'm programming an Activity that launches a second one through
startActivity just like in the Forwarding example. The main difference
is that I'd like to pass some data to the second Activity when
starting it, for example an item selected in a list owned by the first
Activity. I can't find how to do that... Am I missing something? I
guess I do.

Thank you for helping me.

--~--~---------~--~----~------------~-------~--~----~



Passing parameters to new Activity

by Marco Nelissen » Tue, 03 Mar 2009 03:08:45 GMT


 You can add 'extras' to the Intent that you use to start the 2nd Activity.


On Mon, Mar 2, 2009 at 8:34 AM, vincent.gann...@gmail.com



--~--~---------~--~----~------------~-------~--~----~


Sponsored Links


Passing parameters to new Activity

by vincent.gann...@gmail.com » Fri, 06 Mar 2009 21:46:36 GMT


 Works fine! Thanks Marco.
--~--~---------~--~----~------------~-------~--~----~



Other Threads

1. Porting to Acer Aspire

Hi,
  I have an Acer Aspire netbook. I know that Acer is coming up with an
Android Notebook later this year . But is it possible to port Android
to my current Acer Aspire? Is there a pre compiled binary available?

--~--~---------~--~----~------------~-------~--~----~
unsubscribe: android-porting+unsubscr...@googlegroups.com
website: 

2. video display parameters inside android_surface_output significance??

Hi,

What is the significance of displayWidth, displayHeight, frameWidth,
frameHeight parameters inside android_surface_output.cpp??


status_t ret = mSurface->registerBuffers(displayWidth, displayHeight,
frameWidth, frameHeight, PIXEL_FORMAT_RGB_565, mFrameHeap);

 status_t ret = mSurface->registerBuffers(displayWidth, displayHeight,
frameWidth, frameHeight, PIXEL_FORMAT_YCbCr_420_SP, mHeapPmem);


status_t ret = mSurface->registerBuffers(iVideoDisplayWidth,
iVideoDisplayHeight, iVideoWidth, iVideoHeight, PIXEL_FORMAT_YCbCr_420_SP,
mHeapPmem);


I am playing a 320X240 mp4 stream on my 800X480 display panel.The video is
scaled and displaying closer to 800X480.

I was suspecting

displayWidth = closer to 800
displayHeight = closer to  480
(for above Condition maintaining aspect ratio as 320X240)
frameWidth = 320
frameHeight = 240

But when i took the log, i got the values as below.

 displayWidth = 320
displayHeight = 240
frameWidth = 320
frameHeight = 240

I have few doubts:

1. Is this correct??

2.
Is it possible to get the "to be scaled values"  inside
android_surface_output??
I mean in this case the values scaled from 320X240, bit closer to 800X480
and having the same aspect ratio as 320X240??

3.
If not, which part of surface flinger code uses this values for scaling
mostly passed from the window manager??

Regards,
Sreedhar

--~--~---------~--~----~------------~-------~--~----~
unsubscribe: android-porting+unsubscr...@googlegroups.com
website: 

3. Android nearly working on Gumstix Verdex (Intel PXA270)

4. Where can i find the pixelflinger source code ?

5. Export Unsigned Application from two separate projects

6. Animated Sprites For Games

7. IMX31 touch screen issue