I believe I have politely and thoroughly stated my question. Anyone have an answer?
On May 13, 3:20 pm, Keith Wiley <[email protected]> wrote: > Bump. Thanks for any input. > > On May 13, 10:27 am, Keith Wiley <[email protected]> wrote: > > > I have seen a number of threads discussing the deprecation > > ofAbsoluteLayout. I'm a little fearful of reading third-party blogs > > that suggest solutions to the deprecation because in some discussion > > threads the Google employees have explicitly said the blogs contain > > misunderstandings or inaccuracies. > > > So, I need to know how to implement my app's behavior > > withoutAbsoluteLayout. I would greatly appreciate any input people might > > have, especially the real pros, the Android dev team who, by > > deprecatingAbsoluteLayout, must have a clear picture in their heads > > of how to reorganize code to be up-to-date to achieve the same > > functionality. Romain Guy, Diane Hackborn, I'm looking your > > direction. :-) > > > The relevant part of my app is a single large View covering the > > majority of the screen, a subclass of my own creation, whose onDraw > > basically paints a complicated bitmapped canvas. Subsequently, I > > repeatedly add and remove (or set visibility to VISIBLE and GONE, > > that's actually the approach I've taken) an EditText (also subclasses > > with unique behavior) which I must frequently reposition to pixel > > precision over the background canvas. I currently do this by setting > > up a new LayoutParams with the EditText's new location and then > > callingAbsoluteLayout.updateViewLayout on the EditText. Works like a > > charm. > > > So, a single screen-spanning View drawn with a bitmap, overlaid with a > > single EditText which must be positioned to pixel precision, and set > > VISIBLE and GONE periodically, and be moved from location to location > > from time to time. > > > Million dollar question: Without usingAbsoluteLayout, what is the > > official Android/Google endorsed method for implementing this > > behavior? FrameLayout and RelativeLayout seem -- at the least -- > > rather indirect in this situation whereAbsoluteLayoutprovides a > > literal interpretation of my app's behavior: one view positioned > > arbitrarily over another view. Am I incorrect? Can one or both of > > them achieve this behavior as painlessly asAbsoluteLayout? > > > Thank you. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
