i've found a subtle issue with how we queue recalcs of smart objs. if
authorraster <raster@7cbeb6ba-43b4-40fd-8cce-4c39aea84d33>
Mon, 29 Aug 2011 12:14:55 +0000 (12:14 +0000)
committerraster <raster@7cbeb6ba-43b4-40fd-8cce-4c39aea84d33>
Mon, 29 Aug 2011 12:14:55 +0000 (12:14 +0000)
commit393f0abe4500ebee0379ecc3b9d4bc2c3dbe27ba
tree2303a01d791d83ee1734a7ee4364ac4414a1f57d
parent157f45095f69868e79482bcc6016a87ac6d63eb7
i've found a subtle issue with how we queue recalcs of smart objs. if
an obj is already queued we dont push it FURTHEr down the queue if
smart recalc is enabled. now at least we keep order of operation/calc
correctly!

git-svn-id: svn+ssh://svn.enlightenment.org/var/svn/e/trunk/evas@62944 7cbeb6ba-43b4-40fd-8cce-4c39aea84d33
src/lib/canvas/evas_main.c
src/lib/canvas/evas_object_smart.c
src/lib/include/evas_private.h