Updates:
Summary: Moose crashes when importing Citezen
(OrderedCollection(Object)>>doesNotUnderstand: #unsafeAdd:)
Comment #3 on issue 736 by tudor.gi...(a)gmail.com: Moose crashes when
importing Citezen (OrderedCollection(Object)>>doesNotUnderstand:
#unsafeAdd:)
http://code.google.com/p/moose-technology/issues/detail?id=736
(No comment was entered for this change.)
Status: New
Owner: ----
Labels: Type-Defect Priority-Medium
New issue 845 by google....(a)ben.coman.com.au: some Roassal layouts broken
when nested
http://code.google.com/p/moose-technology/issues/detail?id=845
The application I am developing needs to apply layouts to nested elements.
I noticed that some layouts did not work when nested - so I've done a full
review of the layout listed in ROMondrianExample>>chooseLayoutOn: as per
the attached image. On the left is the non-nested-result and on the right
is the nested-result. I have attached the mcz with a slightly modified
#chooseLayoutOn: as well as #chooseLayoutNestedOn: for comparison.
Attachments:
Roassal-BenComan.313.mcz 241 KB
ROMondrianExample-chooseLayoutNestedOn.png 127 KB
Status: New
Owner: ----
Labels: Type-Defect Priority-Medium
New issue 858 by benjamin...(a)gmail.com: Roassal contribution
ROLineEndDiamond
http://code.google.com/p/moose-technology/issues/detail?id=858
I needed a diamond line end symbol to represent aggregation in a UML
diagram, so here it is attached.
Name: Roassal-BenComan.364
Ancestors: Roassal-AlexandreBergel.363, Roassal-BenComan.353
Merge addition of ROLineEndDiamond and ROMondrianExample>>umlAggregateOn:
into mainline (though actually it more catching up ready to merge into
mainline).
Though upon further consideration perhaps 'LineEnd' is not proper, since
someone might want to use it in the middle of a line. Perhaps better
RODiamondLineShape or ROLineShapeDiamond or ROLSDiamond.
btw, since there are many more symbols associated with lines than just
arrows, perhaps consider renaming class ROAbstractArrow something like one
of: ROAbstractLineEnd; ROAbstractLineSymbol; ROAbstractLineShape;
ROLineShape.
Status: New
Owner: ----
Labels: Type-Defect Priority-Medium
New issue 856 by benjamin...(a)gmail.com: ROAbstractElement>>remove
inconsistent nested behaviour
http://code.google.com/p/moose-technology/issues/detail?id=856
I would expect ROAbstractElement>>remove to work consistently whether it
belongs to the top-level view or nested in another element. However it is
not as demonstrate by the code below having this result...
a ROElement<#x>
------
a ROElement<#x>
a ROElement<#y>
=========================================
v := ROView new.
x := ROElement on: #x.
y := ROElement on: #y.
v add: x.
v add: y. "this line different"
y remove.
v allElementsDo: [ :el | Transcript crShow: el ].
Transcript crShow: '------'.
v := ROView new.
x := ROElement on: #x.
y := ROElement on: #y.
v add: x.
x add: y. "this line different"
y remove.
v allElementsDo: [ :el | Transcript crShow: el ].
Status: New
Owner: ----
Labels: Type-Defect Priority-Medium
New issue 852 by benjamin...(a)gmail.com: RORubberband with target
highlighting
http://code.google.com/p/moose-technology/issues/detail?id=852
I have added highlighting of target elements to RORubberband - changeset
attached. Note changeset is against Roassal-AlexandreBergel.343.mcz
since .344 breaks something.
Note2, I renamed RORubberbanding to RORubberband. I had originally been
tossing up between the two, and under further consideration I think the
latter is more appropriate. The former will need to be manually removed.
Attachments:
RubberBand2.3.cs 5.9 KB