| | | |interface Efl.Animator | | | |├ (E) animator,tick
Description
Description
Details
Details
Status | Assigned | Task | ||
---|---|---|---|---|
Resolved | zmike | T7512 efl.ui.layout | ||
Resolved | zmike | T7511 efl.ui.win | ||
Duplicate | singh.amitesh | T5363 Cleanup elm_widget.eo | ||
Resolved | zmike | T7553 efl.ui.widget | ||
Resolved | zmike | T7554 efl.canvas.group | ||
Resolved | zmike | T7555 efl.canvas.object | ||
Resolved | zmike | T7561 efl.animator |
Comment Actions
The only purpose of this interface seems to be to define the animator,tick event and its associated data structure.
Only Efl.Canvas.Object (and Evas.Canvas) implement it.
Seems too simple to have anything wrong. The only question would be if it's worth having it as a separate interface, or should we merge it into Efl.Canvas.Object (and screw legacy! just kidding, should be merged into Evas.Canvas too).
Comment Actions
Hum, it might actually work to move it to Efl.Canvas.Object as we do not have a Canvas object and rely on Efl.Ui.Win for that purpose. Would be interesting to look at this this way. And for the record, I am sure @ManMower will agree, Efl.Animator is the trickiest things to get right!