Right now, TimeMap#setSelected and related methods aren't properly encapsulated
- TimeMapItem is aware of the index-based implementation. This should be fixed,
especially if I ever want to change the selection implementation (e.g. to do
highlights as well) or allow for multiple selections. Top-of-the-head methods:
setSelected(item)
getSelected():item|null
clearSelected(item) // or no item to clear all
State functions will need to be able serialize the selection value. These are
technically methods on TimeMap, though, so I think that these can be internally
aware (i.e. know about the internal representation of selected items).
Original issue reported on code.google.com by nick.rab...@gmail.com on 7 Feb 2011 at 6:47
Original issue reported on code.google.com by
nick.rab...@gmail.com
on 7 Feb 2011 at 6:47