OOT: Trio Data :-)

by Rivelino Satya Nugraha » Fri, 02 Apr 2010 22:26:51 GMT


Sponsored Links
 Salam kenal suhu lesjaw...
Selama ini belum pernah melihat suhu scara langsung euy....
Ada juga om wolwol yah....
Kalo suhu ratjoen.com sering ketemu kalo ke banjarmasin

[feel something different with Android Phone]




eh ada orang ganteng pake topi... :=)) x. ...

*duh sol molo nih...

sent from Milestone2.1 with  | read www.tux.or.id &
 http://bit.ly/aSTXL0for more android info 




-- 
"

To unsubscribe, reply using "remove me" as the subject.



OOT: Trio Data :-)

by Lutfi Hidayat Ramdhani » Fri, 02 Apr 2010 22:28:21 GMT


 Hahaha, om lesjaw melakukan pengakuan

@lutfihidayatr
dikirim dari kaleng ijo yang ada internetnya




eh ada orang ganteng pake topi... :=)) x. ...

*duh sol molo nih...

sent from Milestone2.1 with  | read www.tux.or.id &
 http://bit.ly/aSTXL0for more android info 




-- 
"

To unsubscribe, reply using "remove me" as the subject.


Sponsored Links


Other Threads

1. Detecting Noise

Hi everyone.
I am trying to develop a program which detects noise level of
outside.Is it loud or silent? How loud?

Where should I start? Is there any example ? Any comment will be
greatly appreciated...

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

2. When to setResult for onActivityResult

Hello there ;)

I have some - maybe simple - problem; unfortunately I cannot find a
solution:

I have two activities which communicate via: startActivityForResult(),
setResult(), onActivityResult. I will call the first activity "parent"
and the second one "client", although this may not be technically
correct; so the order of calls must be:

parent.startActivityForResult()
client.setResult()
parent.onActivityResult()

Now, where should I call setResult in the client activity ?

I have already tried various possibilities which have all failed:

 - setResult() in client.onPause() is called TOO LATE; the result has
already been transmitted to the parent (although the method
client.onPause() seems to be called in time).
 - client.onSaveInstanceState() is not guaranteed to be called at all
(and the documentation hints at the same timing problem).
 - The only TECHNICALLY POSSIBLE solution seems to implement a change-
listener for any screen element and set the result there. This may
work in theory, but is NOT VIABLE in practice: (1) it is strenuous and
error-prone for activities with many elements; (2) it gets even more
complicated, when side-effects kick in (change one field in dependency
to another); (3) it is really slow, since one must write ALL contents
any time, a SINGLE element changes (and the generic Intent
communication is already slow by design).

To me, it would seem most natural to overload the onPause() method and
setResult() there - once and for all. There MUST be some easier way
than implementing zounds of listeners ...


Am I overlooking something ? Another listener I haven't stumbled over
yet ? Please prove me wrong ;)

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

3. Can I add a custom qualifier to resource directory?

4. aapt ERROR

5. Need an on-device exception viewer

6. Other payment mechanisms for apps

7. Why adb push to sdcard report "Read-only file system" for the emulator of the latest android source code