On Mon, Aug 2, 2010 at 6:31 PM, Mark Murphy wrote:
> On Mon, Aug 2, 2010 at 5:20 PM, TreKing wrote:
>>> I have read from many sources that findViewById() is a "costly" operation.
>>
>> What sources?
>
> Actually, it's described in several places as being costly, such as
> the books from some "com
On Mon, Aug 2, 2010 at 5:20 PM, TreKing wrote:
>> I have read from many sources that findViewById() is a "costly" operation.
>
> What sources?
Actually, it's described in several places as being costly, such as
the books from some "commons guy". I suspect the source material for
this was some rec
On Mon, Aug 2, 2010 at 12:11 PM, Sebastián Treu wrote:
> I have read from many sources that findViewById() is a "costly" operation.
>
What sources? Define "costly". Sounds like premature optimization. I haven't
looked at the source, but I can't imaging findViewById() does much worse
than a breadt
Hi all,
I'm kind of new to android development. I have read from many sources
that findViewById() is a "costly" operation. I'm making an application
that deals with 5 TextViews to provide different kinds of information
(distance, duration, title, description, etc) from a database. I'm
using listen
4 matches
Mail list logo
