Updates: Labels: Component-Mondrian
Comment #1 on issue 460 by jannik.l...@gmail.com: scaleBy: should be in shapes, and not in MONode http://code.google.com/p/moose-technology/issues/detail?id=460
(No comment was entered for this change.)
Updates: Labels: -Milestone-4.2 Milestone-4.3
Comment #2 on issue 460 by tudor.gi...@gmail.com: scaleBy: should be in shapes, and not in MONode http://code.google.com/p/moose-technology/issues/detail?id=460
(No comment was entered for this change.)
Updates: Labels: -Milestone-4.3
Comment #3 on issue 460 by tudor.gi...@gmail.com: scaleBy: should be in shapes, and not in MONode http://code.google.com/p/moose-technology/issues/detail?id=460
(No comment was entered for this change.)
Updates: Status: WontFix
Comment #4 on issue 460 by alexandr...@gmail.com: scaleBy: should be in shapes, and not in MONode http://code.google.com/p/moose-technology/issues/detail?id=460
I have doubt about it.
Comment #5 on issue 460 by tudor.gi...@gmail.com: scaleBy: should be in shapes, and not in MONode http://code.google.com/p/moose-technology/issues/detail?id=460
I believe this should be in the canvas.
Comment #6 on issue 460 by alexandr...@gmail.com: scaleBy: should be in shapes, and not in MONode http://code.google.com/p/moose-technology/issues/detail?id=460
It is currently in MORoot. But a node (or a shape) has to be able to scale itself. If it is solely defined on MOCanvas, then the canvas has to modify the bounds of the node, which is not nice.
Comment #7 on issue 460 by tudor.gi...@gmail.com: scaleBy: should be in shapes, and not in MONode http://code.google.com/p/moose-technology/issues/detail?id=460
No. I meant the real canvas. The node should not know about zooming. This should be handled transparently by the infrastructure.
In VW we had a wrapper that handled the zooming.
-
moose-technology＠googlecode.com