[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[E-devel] evas_smart_new() api

A while back, layer and stacking handling for smart object members was
moved into evas itself, removing the need for the layer_set, raise,
lower, stack_above and stack_below callbacks. However, the api remained
the same, so now every smart object has 5 NULL's in the middle of its
evas_smart_new() call.

Any objections to removing these from the API (other than the fact that
we have to trudge through cvs and delete a bunch of NULL's)? I'd prefer
this to having deprecated API on release.

(and yes, i'd be willing to do most of the work) :)