Status: New
Owner: ----
Labels: Type-Defect Priority-Medium Component-Glamour
New issue 801 by tudor.gi...(a)gmail.com: MorphTreeMorph does not properly
support custom selection on Windows
http://code.google.com/p/moose-technology/issues/detail?id=801
Open a MorphTreeMorph and then try to press Alt+Click to select multiple
elements. This does not work on Windows (but it works on Mac using Command).
However, selecting a range using Shift+Click works just fine.
Status: New
Owner: ----
Labels: Type-Defect Priority-Medium
New issue 857 by benjamin...(a)gmail.com: ROCircle strange MNU #extent:
http://code.google.com/p/moose-technology/issues/detail?id=857
With ConfigurationOfRoassal.667 just loaded, my project application popped
up a 'MNU: receiver of "extent:" is nil, but as you can see in the attached
screen snapshot, which has the default debugger highlighting showing the
current executiong, the receiver is the ivar 'next' which is actually _not_
nil, but an instance of RONullShape. Strange...
As a test case, executing the following in Rossal Easel caused the same MNU.
=========
rawView add: (ROElement on: 1) + ROCircle.
=========
Fixed it with: Compiler recompileAll. This actually has happened to me a
few times in past couple of weeks.
(Note actually the example code gives a really tiny circle and #spriteOn:
would have been better than #on:)
Attachments:
ROCircle-MNU-extent.png 34.6 KB
Status: New
Owner: ----
Labels: Type-Defect Priority-Medium Component-Glamour Milestone-4.7
New issue 800 by tudor.gi...(a)gmail.com: Glamour browsers do not respond to
browser-global keybindings
http://code.google.com/p/moose-technology/issues/detail?id=800
Essentially, window does not seem to be affected by this line:
window on: #keyStroke send: #handleKeyStroke: to: window.
This seems to be a Pharo 1.4 related issue.
Status: New
Owner: ----
Labels: Type-Engineering Priority-Medium Milestone-4.7
New issue 853 by tu...(a)tudorgirba.com: ConfigurationOfMoose should be split
to reflect core vs suite
http://code.google.com/p/moose-technology/issues/detail?id=853
Right now, in ConfigurationOfMoose we have two methods:
- coreDefault
- default
These should be the basis for splitting into two distinct configuration
classes.
Ideally, we would rename ConfigurationOfMoose to ConfigurationOfMooseSuite,
but this is difficult due to the many scripts that depend on the current
name. So, we will not do that (at least not now).
Also, in the process of splitting, we will remove the 'default' version and
transform it into a baseline.
Status: New
Owner: ----
Labels: Type-Enhancement Priority-Medium
New issue 716 by jannik.l...(a)gmail.com: span or size for each column in
GLMTablePresentation
http://code.google.com/p/moose-technology/issues/detail?id=716
I am using GLMTablePresentation, and I would like to specify span or size
for each column.
To do that:
Extend the GLMTablePresenation, and the associated rendering.
Status: New
Owner: ----
Labels: Type-Defect Priority-Medium
New issue 748 by cy.delau...(a)gmail.com: DistributionMap examples not working
http://code.google.com/p/moose-technology/issues/detail?id=748
When you try to execute the examples in the class side of DistributionMap,
you get an error.
This bug looks complicate and it does not seem to be related to
distributionMap:
When I debug and I go down to the method
DistributionMap>>elementsWithProperty:inPart:
If I insert this lign:
(elementsAndPropertyValue keys detect: [:each | each ==
element]).
it returns me one element.
Then if I execute:
(elementsAndPropertyValue at: element)
I have a KeyNotFound error
Status: New
Owner: jannik.l...(a)gmail.com
Labels: Type-Defect Priority-Medium Component-DSM Milestone-4.4
New issue 555 by jannik.l...(a)gmail.com: DSM improve visualization
http://code.google.com/p/moose-technology/issues/detail?id=555
I made the structure for DSM visualization.
Now, I should create script for each and make communications between them
coherent.
Comment #1 on issue 432 by tu...(a)tudorgirba.com: Popup should appear only
when a certain modifier key is pressed
http://code.google.com/p/moose-technology/issues/detail?id=432
Another option would be to have the rendering happening in another thread.
Status: New
Owner: ----
Labels: Type-Defect Priority-Medium
New issue 829 by google....(a)ben.coman.com.au: Roassal Label Text does not
scale with Zoom Out
http://code.google.com/p/moose-technology/issues/detail?id=829
Actions
1. Open Roassal Easel > Example > #arrowed edges > umlLike
2. Click the <Zoom out> button multiple times
Expected Behaviour
Text gets smaller so as to stay within the border as the label box gets
smaller.
Observed Behaviour
Only the border of the label gets smaller. The text gets the same size
until it all overlaps.