evas evas_object_smart.c: Reverted smart callback calling sequence.
Now, smart callback is prepended among the same priorities. After the discussion with hermet and raster. I fixed this because I think it's better keeping the default behavior even we have new priority option. This is for evas backward compatibility and for the world peace. Although I know there is no official policy and it's not recommended to rely on the smart callback calling sequence in application, I really hope evas needs to have compatibility. Otherwise we need to adopt the new policy in next version of evas. SVN revision: 62792
This commit is contained in:
parent
fc4c7aa7a0
commit
733ac6e274
|
@ -333,8 +333,6 @@ _callback_priority_cmp(const void *_a, const void *_b)
|
|||
b = (const Evas_Smart_Callback *) _b;
|
||||
if (a->priority < b->priority)
|
||||
return -1;
|
||||
else if (a->priority == b->priority)
|
||||
return 0;
|
||||
else
|
||||
return 1;
|
||||
}
|
||||
|
|
Loading…
Reference in New Issue