Rather than going off on me and TreKing and acting like we are idiots -- how about instead, you focused on communicating better what you are doing?
I am sure TreKing knows what a radio button is. The phrase "light up a radio button" is rather ambiguous, however. Focused? Checked? There are actual technical terms that make it precise, but you're not using them. You're also not making it clear just what you are doing with radio buttons -- just what layout you're using, what you're doing, etc. Sure I know about row layouts. There's an uncountable number of possible layouts you could be using, involving one or more radio button. The problem here isn't that we're idiots. It's that we can't read your mind very clearly, and the signal justs gets worse when you get all angry and sarcastic. Yes, I know writing good questions is hard. But not quite as hard as dealing with the responses you get (or silence) when you don't. I still have little idea what you were doing, what problem you encountered, and subsequently, what "obvious" solution you found. I don't much care, since your problem is solved; I was just explaining a major factor in why you didn't get an answer. I wasn't even getting down on your case for it. In contrast to this message, in which I am explicitly down on your case for ranting at us. But otherwise, we're cool. If you really wanted to be helpful, you could explain for the benefit of those new to ListView and adaptors just what the problem was and how to overcome it. That would be generous of your time, but entirely at your option. On Apr 7, 2:58 pm, DonFrench <[email protected]> wrote: > Sure, I guess if you have never read anything about specifying a row > template when instantiating an ArrayAdapter or checked out the > APIDemos example, you never would have heard of the single choice > layout that displays a radio button on every list item. But my guess > is that most people who have done any work with ListViews are at least > aware of this very basic and useful feature. > > On Apr 7, 11:35 am, Bob Kerns <[email protected]> wrote: > > > > > Perhaps -- but since I don't really understand the question, perhaps > > question quality had something to do with it? > > > "The radio button". What radio button? > > > What's a "a simple_list_item_single_choice layout"? > > > These things probably seem obvious to you, but they're not to me. So I > > can only guess at the obvious solution. It could also be that I don't > > even KNOW the solution. > > > I spend too much time answering questions as it is. If I don't > > immediately understand the question enough (or a response) to have > > something to offer, I just skip on to the next message. > > > Even good, easy questions can go unanswered. You can improve the odds > > by writing clear questions, easily grasped by someone just scanning, > > yet complete enough to fully understand. > > > That's not easy -- and even if everyone suddenly managed to do it, > > it'd just increase the competition for answers to good questions! > > > On Apr 7, 9:17 am, DonFrench <[email protected]> wrote: > > > > On Apr 7, 8:14 am, "~ TreKing" <[email protected]> wrote: > > > > > On Tue, Apr 6, 2010 at 7:44 PM, DonFrench <[email protected]> wrote: > > > > > And the truth is that even then the odds are that no one will answer > > > > > you. > > > > > I highly disagree. > > > > > > I recently posted a very simple and clear one-sentence question > > > > > Which was what, out of curiosity? > > > > This one: > > > http://groups.google.com/group/android-developers/browse_thread/threa... > > > > > > that I know a high percentage of the people on this list knew the > > > > > answer > > > > > to. > > > > > And you know this for a fact how? > > > > Because when I found the answer for myself, I saw that it was > > > something that any experienced Android developer would probably know. > > > > > > Trying to figure out how to get an answer from this group is a puzzle > > > > > in > > > > > itself. > > > > > The problem is that on these Android groups a lot of people post things > > > > like > > > > "URGENT!: my app doesn't work, why?", or, like in this case, large > > > > chunk of > > > > alien code with no context, or "here's a picture of what I want to do, > > > > how > > > > do I do it?", or other equally vague and generic posts that would take > > > > hours > > > > to answer completely. > > > > > I don't know about the rest of the group, but I'm more inclined to help > > > > where I can when 1) The post is clear, concise, and specific (not "it > > > > doesn't work") and 2) The person indicates that they've put time and > > > > energy > > > > into solving the problem and they've narrowed it down to something > > > > specific > > > > (they Googled with no result, they checked the debug log with nothing > > > > obvious, they've tried A, B, C, and D with no luck, etc). > > > > > --------------------------------------------------------------------------- > > > > ---------------------- > > > > TreKing - Chicago transit tracking app for Android-powered > > > > deviceshttp://sites.google.com/site/rezmobileapps/treking -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en To unsubscribe, reply using "remove me" as the subject.
