Thanks.
It would be nice if there was a cleaner failure rather than just showing
you the wrong source. I wouldn't mind some kind of check that prevents you
from jumping to some weird source line without necessarily knowing it.
On Thursday, January 10, 2013 9:25:20 AM UTC-6, Streets Of
This occurred on the Nexus 7 tablet, and the Android version was 4.2.1.
On Wednesday, January 9, 2013 7:46:34 PM UTC-6, RichardC wrote:
Emulator or Phone and what was the Android version running on it?
On Wednesday, January 9, 2013 10:40:27 PM UTC, bob wrote:
I'm stepping thru my source.
It seems to work if I do Edit Source Lookup and change it to android-17.
Is it 17 because the Nexus 7 is running 4.2.1?
I built targeted for 16.
On Wednesday, January 9, 2013 7:46:34 PM UTC-6, RichardC wrote:
Emulator or Phone and what was the Android version running on it?
On
Yes.
The code on the device (Nexus 7) has debug info that tells Eclipse the
line-numbers of the source-code. If your source-code (android-16) is
out-of-date, these line-number don't match up and Eclipse shows you
something wrong (correct line-number, wrong source-version).
On Thursday,
Emulator or Phone and what was the Android version running on it?
On Wednesday, January 9, 2013 10:40:27 PM UTC, bob wrote:
I'm stepping thru my source.
I have a call to invalidate().
I stepped into it, and attached the android source (version 16).
However, it went here:
/**
*
5 matches
Mail list logo
