Re: Android: create drawable from path

From:

Patricia Shanahan <pats@acm.org>

Newsgroups:

comp.lang.java.programmer

Date:

Fri, 15 Apr 2011 09:25:17 -0700

Message-ID:

<o4ednUsm87v17DXQnZ2dnUVZ_vmdnZ2d@earthlink.com>

On 4/15/2011 3:38 AM, Dirk Bruere at NeoPax wrote:

On 15/04/2011 05:20, Patricia Shanahan wrote:

On 4/14/2011 6:20 PM, Dirk Bruere at NeoPax wrote:

On 15/04/2011 01:28, Patricia Shanahan wrote:

On 4/14/2011 4:52 PM, Dirk Bruere at NeoPax wrote:

On 14/04/2011 23:32, Lew wrote:

...

That information was *not* in your post, so no, there was *not*
enough
information in your post. I am happy that we found the correct answer
despite that. It is strange that you're claiming to have provided
enough
information by citing data that you did not provide us.

Because at the time I did not know it was relevent

That is the perfect summary of the argument in favor of constructing
and
posting an SSCCE.

An SSCCE includes all actually relevant information, regardless of
whether the person constructing the SSCCE is aware of its relevance.

Constructing a non-SSCCE excerpt the contains all information that is
actually relevant is much harder. It requires the programmer to know
what is relevant to the problem without knowing enough to solve it, a
rare condition.

Patricia

Well, I have just got another problem that cannot be done this way,
unless I post the whole program.

I have multiple listviews each containing hundreds of strings.
I switch between them with various buttons.
When they load, they are fine.
However, if I use a finger to scroll the screen up and then switch to
another listview while the last one is still scrolling I get entries
broken into multiple lines that persist.

It sure sounds like SSCCE material to me. I would start with questions
like how many listviews are needed, and how many strings per view.

4 listviews, with between 100 and 2000 strings in each

My bug, Android 2.2 bug or h/w problem?

If this happened in non-Android Java, I would suggest checking that all
GUI activity is on the event dispatching thread. It sounds as though the
view change is being processed before the scroll has finished, which
should be prevented by doing both in the same thread.

Maybe you should do the equivalent check?

Yes.
Anyway, its not a major bug - there are other things to do first

Incidentally, this is a case where the building-up approach to an SSCCE
might be helpful. If you wrote an SSCCE from scratch, it could have the
right number of listviews and strings, but would probably not share any
program bugs. You could use a string generator to get the thousands of
strings in a short program.

If it runs correctly, the problem is more likely to be in your program.
If it reproduces the failure, it is more likely to be hardware or system
software.

Patricia