Dok2Go

by Justinus Adrianto » Fri, 26 Feb 2010 11:19:31 GMT


Sponsored Links
 Rekan2

Adam yg punya + utk liat pdf

*met long weekend all
...mmmm japri ya
~ white dream ~

-- 
"



Dok2Go

by Lesjaw鈩?鈾 » Fri, 26 Feb 2010 11:27:47 GMT


 bos, next time japri yak...pan bos ah dah bilangin... ;-)

sent from Pulsar 1.1




maaf, ini ada key nya. tp untuk docstogo nya ndiri harus donlot sendiri



-- 
"


Sponsored Links


Dok2Go

by christian soesilo » Fri, 26 Feb 2010 11:29:42 GMT


 oya maap lupa

-- 
"



Other Threads

1. : How to stops the activity from getting restarted when mode changes from LandScape to Portrait or vice-versa

Given that the screen probably has to rerender the layout as a result
of the change in orientation, I really doubt that's the case.  I'm
also not sure why it would be a pressing issue, since the functions it
uses to do so are things you have to write anyway for normal app
operation.

If you want to force a particular layout each time, however, you can
specify that in the manifest file using android:screenOrientation for
that particular activity.

The screen doesn't flicker (at least in the emulator), but I have no
idea if it will still go through the lifecycle changes as a result.



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

2. activity doesn't seem to end, despite calling .finish()...

Hi all,
Here's my oddity:
I have two emulators communicating via TCP.  Each emulator has two
threads - one running a server, and the other running a client.  Each
thread is in a loop, waiting until that thread gets a connection
(socket) with the other emulator.  Once a thread gets a connection, it
calls a synchronized method - doSomething().  Since each thread
(server and client) is vying for the same synchronized method, only
one thread is active at a given time. For instance, first Emulator1
will have an active server connected to client of Emulator2. Then when
this finishes, Emulator2 may be the server for Emulator1's client.
etc.

This all seems to work. Except, for....
when I force one emulator's server to exit its perpetual loop of
accepting inbound connections, that emulator finishes its server
thread and sets a flag which returns to the main activity which then
calls the .finish() method on the main activity.  The main Activity
appears to end normally. (The screen returns to the "home" screen of
the emulator).   However, the activity continues to act as a server
for the other emulator, accepting inbound connections forever.  The
only way to stop the connections is to close the emulator.  (It
doesn't stop the problem if I just click the "return" key or "home"
key on the emulator.)

Other details:
Before calling finish(), I specifically close() the serverSocket and
other sockets I have been using.
I have not specifically called my threads as services (which I know
can run in the background). I have just executed the threads in my
main activity as standard java threads...

I really don't understand why this should be happening.
Thanks for any insight!
Jim



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

3. "Wiring" emulator services to PC's

4. Carrymobile 's HTC Dream/T-Mobile G1/Google Andriod leather case released

5. pop3

6. G1 Leather Case

7. Nested Call Log