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: ----
CC: alexandr...(a)gmail.com
Labels: Type-Defect Priority-Medium Component-Roassal Component-Glamour
New issue 870 by tu...(a)tudorgirba.com: ROFocusView focuses on the wrong spot
http://code.google.com/p/moose-technology/issues/detail?id=870
Open a Roassal Easel and paste this:
| node |
node := view node: #a.
ROFocusView new on: node view: view raw.
The node is selected somewhere at the bottom. The reason is likely to be
that the canvas has a static size, instead of adapting by default to the
size of the surrounding pane
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 OpSys-All Milestone-4.7
New issue 871 by tu...(a)tudorgirba.com: One click distribution has old vms
http://code.google.com/p/moose-technology/issues/detail?id=871
We need to update the VMs for the one click distribution.
Status: Accepted
Owner: kurs....(a)gmail.com
CC: tudor.gi...(a)gmail.com
Labels: Type-Defect Priority-Medium Component-PetitParser
New issue 881 by kurs....(a)gmail.com: Missing browser instance variable
http://code.google.com/p/moose-technology/issues/detail?id=881
PPParserBrowser and PPAllParserBrowser are missing browser instance
variable, since the supperclass was changed from BrowserTemplate to
CompsoitePresentation (PetitGui.107).
I presume, this is minor issue, but I have no idea why it was changed from
Template to CompositePresentation.