Barak, Ron wrote: > Did any of you made an extension to FloatCanvas, whereby this problem > could not happen ?
Tree.py is a small demo that I wrote to demonstrate how one might build a tree-type graphic. It was never intended to be feature-complete. I did write it because someone wanted to do that kind of thing, so perhaps they've improved upon it. The key point is that FloatCanvas is a drawing tool, it takes care of handling buffering, paint events, hit-testing, scaling, etc. It's designed to be flexible and usable for a wide variety of graphics. However, it is designed to be a base on which one can build various applications, rather than having everything built-in. What all that means is that you will need to design the layout logic yourself -- what's in Tree.py is very simple code that I whipped up, its going to need some work to get it do all you need. > Namely - if two objects are to be mapped to the same spot on the canvas, > something would happen (e.g., an exception would be raised, the > placements would be changed, etc.). If you look at the LayoutTree() function, it is very simple --you'll need to add a fair bit to that to make it work. -Chris -- Christopher Barker, Ph.D. Oceanographer Emergency Response Division NOAA/NOS/OR&R (206) 526-6959 voice 7600 Sand Point Way NE (206) 526-6329 fax Seattle, WA 98115 (206) 526-6317 main reception [EMAIL PROTECTED] _______________________________________________ FloatCanvas mailing list [email protected] http://mail.mithis.com/cgi-bin/mailman/listinfo/floatcanvas
