Actually, my preference is to use graphics for those two, if one is
expecting to do much localization. A left-pointing red arrow or an
"X" in a circle can mean "cancel", while a right-pointing green arrow
or a check mark can mean "OK".
On Oct 14, 12:27 pm, Kostya Vasilyev wrote:
> 14.10.2010 2
14.10.2010 21:13, DanH пишет:
The only reason for using them (vs your own values) is to save
yourself the trouble of translating your own "yes/no" values should
you decide to support another language.
Even then, an application that only has those two strings in the current
language, out of its
They're defined like they're defined -- if they were changed then a
lot of applications would be "broken", whether changing them "makes
sense" or not.
The only reason for using them (vs your own values) is to save
yourself the trouble of translating your own "yes/no" values should
you decide to su
I know that, but why there are constants named with "yes" and "no" but
containing "ok" and "cancel"? Is it common to answer a yes/no question
with ok/cancel? I hate this bad habit, because they sound not logical.
Sincerely
xZise
On Oct 13, 8:19 pm, DanH wrote:
> Define your own application-local
Define your own application-local R.string values. How to define
string resources is one of the first things you should learn about
Android development.
On Oct 12, 3:23 pm, xZise wrote:
> Hello, I want to display a simple dialog to ask if somebody has done
> something.
>
> public class YesNoTest
5 matches
Mail list logo
