Hi Dianne, One of the persistent problems I've had over the years developing GUIs, whether it be MFC, wxWndows, Swing, or now Android, has been understanding the exact flow of events within the framework. All is well if simply overriding onItemClick() is enough to get the job done. But as soon as an app starts getting complicated, and I need to do something a little different it can become a lesson in frustration trying to get that event to fire in the right place at the right time. Once you put class inheritance (i.e. overrides and handler functions), view hierarchies (i.e parent-child relationships), and runtime listeners, all in the pot, it's anyone's guess where that event will end up, or how best to do what you want. Given the framework soure code, you can try and follow the chain of events, but that is often impossible; without it, well, google is your friend.
One example of frustration from my Android experience was trying to get checkbox views clicking independently of a list view row (i.e. *not* like the CheckBoxPreference), and still behaving normally in all other respects. So my question: is there a high level overview of the framework design philosophy, how it fits together, and specifically, the routing algorithms for events. I think I've read the sdk docs inside out now and I haven't seen one. It would be very helpful. thanks and regards, Craig --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "android-framework" 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-framework?hl=en -~----------~----~----~----~------~----~------~--~---
