aboutsummaryrefslogtreecommitdiffstats
path: root/legacy/evas/src/lib/canvas/evas_clip.c
diff options
context:
space:
mode:
authorCarsten Haitzler <raster@rasterman.com>2010-09-01 21:38:34 +0000
committerCarsten Haitzler <raster@rasterman.com>2010-09-01 21:38:34 +0000
commit29f59da989b778dd691166506533866782f3b219 (patch)
tree9675b1d9bc21acbf28e10a71cb11287efa8feca7 /legacy/evas/src/lib/canvas/evas_clip.c
parentnow that mostly fixes this map clip issue... ugh. took a while to come up (diff)
downloadefl-29f59da989b778dd691166506533866782f3b219.tar.gz
comment++
SVN revision: 51824
Diffstat (limited to 'legacy/evas/src/lib/canvas/evas_clip.c')
-rw-r--r--legacy/evas/src/lib/canvas/evas_clip.c5
1 files changed, 2 insertions, 3 deletions
diff --git a/legacy/evas/src/lib/canvas/evas_clip.c b/legacy/evas/src/lib/canvas/evas_clip.c
index 2bfa70fa83..6b0ae2bdf5 100644
--- a/legacy/evas/src/lib/canvas/evas_clip.c
+++ b/legacy/evas/src/lib/canvas/evas_clip.c
@@ -68,6 +68,8 @@ evas_object_clippers_was_visible(Evas_Object *obj)
* breaks in logic, or nasty re-work of apps or4 the whole concept of clipping,
* smart objects and maps... and that will have to wait for evas 2.0
*
+ * the below does clip fixups etc. in the even a clip spans a map boundary.
+ * not pretty, but necessary.
*/
#define MAP_ACROSS 1
@@ -105,9 +107,6 @@ evas_object_clip_across_check(Evas_Object *obj)
// this function is called on an object when map is enabled or disabled on it
// thus creating a "map boundary" at that point.
-//
-// FIXME: smart member add/del and clip set/unset needs to check the new
-// smart parent (if any)
void
evas_object_mapped_clip_across_mark(Evas_Object *obj)
{