24 Apr
2014
24 Apr
'14
8:44 p.m.
What Doru wants is quite complex. It does not mean draw one shape above another. But also
be able to define that I want to have those elements inside the second shape, another
elements above third area. Like UML class. It has three parts. One for name, one for
fields, one for methods. You want to do separate nesting for fields and for methods. And
soon someone will want different interactions for each shape. For example different click
actions, different context menus, etc.
In Roassal1 there is also resize strategy, so if someone moves nested elements, it should
change shape size or disable to move the nested element outside the UML shape.
Cheers,
Jura
El 24-04-2014, a las 9:58, Alexandre Bergel <alexandre.bergel(a)me.com> escribió:
Thanks to all the discussion we are having, I am
realizing that RTLabelled is wrongly defined. This is not the way to go. What we need,
(listen Doru), is a nice composition mechanism for shapes.
What we have now works okay for other things than Label. Label do not work for now. I am
working on it right now…
Alexandre
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
On Apr 24, 2014, at 7:49 AM, Leo Perard <leo.perard(a)gmail.com> wrote:
Hi,
When I remove an element from the view and this element had an interaction RTLabelled,
the label is not removed.
| view el |
view := RTView new.
el := (RTBox new size: 20; color: Color blue) elementOn: 'Element'.
view add: el.
el @ RTLabelled.
el on: TRMouseClick do: [ :event | el remove. view canvas signalUpdate ].
view open
--
Leo Perard
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev