The suggestion to avoid using private APIs is wise. I had a company once
that built a model on WinNT 4 and when XP/5.0 came out was rendered
obsolete.
Just sayin' is all.
- C
--
You received this message because you are subscribed to the Google
Groups Android Developers group.
To post to
Of course, it's wise, but frankly, only an idiot would use that piece
of code -- and you cannot really help those people.
On Jun 2, 2:00 pm, Chris crehb...@gmail.com wrote:
The suggestion to avoid using private APIs is wise. I had a company once
that built a model on WinNT 4 and when XP/5.0
Common guys. Give him a bit of credit.
Yes. I agree it is a GOOD recommendation to not use private APIs. It
is especially good recommendation to not use them for a general
purpose facility.
Other than that it is a good effort.
Someone thinks differently let him experiment.
Satya
On Thu, Jun
Experimentation is good.
But the post is encouraging to actually use it in actual applications.
And so far, i haven't seen a use-case that can only be solved by using modal
dialogs that 'block' the calling UI thread. Calling 'showDialog(id)'
(pre-Fragment period) makes your underlying activity
Why do you care? If people are stupid enough to use it, they deserve
that their apps break.
On Jun 2, 12:35 pm, Dianne Hackborn hack...@android.com wrote:
And dang it, stop telling people to do this.
On Wed, Jun 1, 2011 at 9:32 PM, Dianne Hackborn hack...@android.com wrote:
You are
I care because I don't want to break people's applications.
On Wed, Jun 1, 2011 at 10:21 PM, Zsolt Vasvari zvasv...@gmail.com wrote:
Why do you care? If people are stupid enough to use it, they deserve
that their apps break.
On Jun 2, 12:35 pm, Dianne Hackborn hack...@android.com wrote:
6 matches
Mail list logo