Compiling against a *REAL* android.jar in eclipse???

by Dianne Hackborn » Tue, 28 Apr 2009 11:30:33 GMT


Sponsored Links
 orrect.  Don't do this.  Your code will break in the future.  That is why
these fields are hidden.

For scrolling, you can use the method to set the scroll position.

For the background, if the normal background image doesn't do what you want,
then implement your own background drawing. Clearing and re-setting the
background field is clearly relying on implementation details that can
change in future versions.

If there are specific features you find are missing, you can file feature
requests or (more likely to have a result) submit patches to add those
features. For the latter, though, keep in mind that we are very restrictive
on accepting changes to fundamental parts of the system like this.

On Mon, Apr 27, 2009 at 8:13 PM, Peter Carpenter <
peter.carpen...@skytechnologies.com> wrote:



--
Dianne Hackborn
Android framework engineer
hack...@android.com

Note: please don't send private questions to me, as I don't have time to
provide private support, and so won't reply to such e-mails. All such
questions should be posted on public forums, where I and others can see and
answer them.

--~--~---------~--~----~------------~-------~--~----~



Compiling against a *REAL* android.jar in eclipse???

by Peter Carpenter » Tue, 28 Apr 2009 11:50:46 GMT


 hanks Dianne, makes sense.



With the scrolling - I wanted to essentially copy the code used for
vertical scrolling and implement it for horizontal (like others have
done) However this won't compile due to inability to access the
protected member variables. There was no function that would
setScrollX() without calling invalidate() etc. But, this component will
apparently exist in 1.5, so there's light at the end of the tunnel for
this one.





With regards to the button example though, it looks like I can't win
either way ...

* If I implement my own background drawing, it won't be compatible with
future versions (Because I can't reference the existing button images
and therefore if the images change in later versions I can't get them)

* If I modify the code and the mechanism for drawing buttons changes, it
will break.



Looks like the best thing to do is wrapper the StateListDrawable in this
case then. :-(



Cheers,



Peter.



________________________________

From: android-developers@googlegroups.com
[mailto:android-develop...@googlegroups.com] On Behalf Of Dianne
Hackborn
Sent: Tuesday, 28 April 2009 1:30 PM
To: android-developers@googlegroups.com
Subject: [android-developers] Re: Compiling against a *REAL* android.jar
in eclipse???



Correct. Don't do this. Your code will break in the future. That is
why these fields are hidden.

For scrolling, you can use the method to set the scroll position.

For the background, if the normal background image doesn't do what you
want, then implement your own background drawing. Clearing and
re-setting the background field is clearly relying on implementation
details that can change in future versions.

If there are specific features you find are missing, you can file
feature requests or (more likely to have a result) submit patches to add
those features. For the latter, though, keep in mind that we are very
restrictive on accepting changes to fundamental parts of the system like
this.

On Mon, Apr 27, 2009 at 8:13 PM, Peter Carpenter
<peter.carpen...@skytechnologies.com> wrote:

Hi Dianne,



Thanks for replying.



I want to create custom GUI components and access things like
View.mScrollX which has no setFunction (to create a horizontally
scrolling view), and mBGDrawable which does have a set function - but
that does a whole heap of stuff I don't want it to do.



Essentially with the second option, I would like to have an image button
using all of the standard background drawables (but hide only the
default standard enabled state image). I can't find API's that let me
do any of this cleanly. The only way I can currently find is to
intercept the draw function and hide the background temporarily. It
would be nicer to be able to either create my own StateListDrawable
using the existing button background drawables (which are not public) or
else have a removeState function in the StateListDrawable.



So essentially you are saying I shouldn't be doing this???



Cheers,


Peter.



________________________________

From: android-developers@googlegroups.com
[mailto:android-develop...@googlegroups.com] On Behalf Of Dianne
Hackborn
Sent: Tuesday, 28 April 2009 1:02 PM
To: android-developers@googlegroups.com
Subject: [android-developers] Re: Compiling against a *REAL* android.jar
in eclipse???



Don't do that. If you aren't writing an app


Sponsored Links


Other Threads

1. OOT: Tethering made easy: SIMFi is a SIM card with built-in Wi-Fi router

Some mobile phones can do Wi-Fi tethering, others need to connect to the PC
Suite for Internet sharing and some just can't do it, period. But what if
the SIM card in the phone could do it all by itself? Sagem Orga and
Telefonica have come up with such a SIM card, dubbed SIMFi.

SIMFi is compatible with existing phones but acts as a Wi-Fi router that any
device can connect to. The Wi-Fi gadgetry is integrated into the card
itself, but we guess you'd still need a phone with good 3G connectivity to
source the data connection in the first place.

More information should be revealed at the MWC next week and hopefully some
nagging questions about SIMFi will be answered, like how good a Wi-Fi radio
have they managed to fit into the SIM card form-factor and what kind of
strain that will put on the phone's battery.

Anyway, this has the potential to become highly popular for customers with
solid data plans. Get a SIMFi card with a data plan and you can use it both
for your phone and laptop/netbook with no hassle - no moving the card back
and forth between the phone and modem or worry about PC Suites or tethering
hacks.

-- 
"Indonesian Android Community [id-android]" 

2. how to draw a popup rectangle on google map .. plz help

> hello. I am able to draw a marker image on specific locations on

Use a RelativeLayout as the container for both the map and some other
layout that is your popup. Give the popup android:visibility="gone" in the
layout XML. When you want to show the popup, call
setVisibility(View.VISIBLE) on it.

Getting it "exactly above the marker" may be difficult, as I am not sure
how you can find out the pixel location of the marker.

-- 
Mark Murphy (a Commons Guy)
http://commonsware.com
Android App Developer Books: http://commonsware.com/books.html


--

3. how to draw a popup rectangle on google map .. plz help

4. Sony Ericsson X10 Launch

5. Layar miley ga respon-Need help

6. Porting android on adsl router

7. Layout Highlight For Already Background Set