Really annoying that Date/Time are final classes as well so you can't
extend them.
Lee
On Sep 8, 8:46 pm, Armond Avanes armond...@yahoo.com wrote:
Thanks for your answer... Yes, copying the source code will be the worse
case but how about the future changes and improvements to these
Lee,
Take a look at android.widget.DatePicker and android.widget.TimePicker
source codes, and you'll notice that they're using date_picker.xml and
time_picker.xml as they layouts. So far so good! Now take a look at
date_picker.xml source code and see those
So by extending these two classes, I can't see a way to do what I want. I
have to somehow deal with those internal API, unless I copy the whole code
and deal with my own version of DatePicker/TimePicker/NumberPicker from
scratch. Correct me if I'm wrong...
No, sure, I agree.
I was just
You could always roll you own skinnable version, borrowing from the
original source code.
Yusuf Saib
Android
·T· · ·Mobile· stick together
The views, opinions and statements in this email are those of the
author solely in their individual capacity, and do not necessarily
represent those of
Thanks for your answer... Yes, copying the source code will be the worse
case but how about the future changes and improvements to these components?
The change management will be a headache.
After all, why is it so? Almost all components are skinnable... why not
these ones? Does this mean that
5 matches
Mail list logo
