On Wed, 25 Apr 2018 13:23:49 +0900 Hermet Park <[email protected]> said:
> Hi. > > As I checked evas_object_geometry_set() or efl_gfx_geometry_set(), > It triggers resize, move callbacks individually. > > Well, I assume user scenario, > they may need just one event callback for the geometry changes if they like > to avoid duplicated tasks due to each callbacks - move and resize. > > I guess geometry callback is make sense to me. What do you think? hmmm. for legacy - no. but for eo interfaces i think actually moving from a move and resize event to a single geometry change event would be better. my reasoning - cost of event handling. the more events you produce, the more it costs to go look for someone who handles that event and then call them. as an aside: we probably should optimize eo's event calling likely with a small cache of the last 1-4 event descriptions and a small array of callbacks to call. it's a memory vs speed tradeoff though. it should be simple to just build with an LRU etc. and totally throw it all away if an callback is added or removed (and rebuild as events are called). > -- > Regards, Hermet > ------------------------------------------------------------------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > _______________________________________________ > enlightenment-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/enlightenment-devel > -- ------------- Codito, ergo sum - "I code, therefore I am" -------------- Carsten Haitzler - [email protected] ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ enlightenment-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
