Moose-dev October 2012

moose-dev@list.inf.unibe.ch

25 participants
139 discussions

Issue 801 in moose-technology: MorphTreeMorph does not properly support custom selection on Windows
by moose-technology＠googlecode.com 07 Jul '13

07 Jul '13

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.

1 1

Issue 857 in moose-technology: ROCircle strange MNU #extent:
by moose-technology＠googlecode.com 07 Jul '13

07 Jul '13

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

1 9

Issue 800 in moose-technology: Glamour browsers do not respond to browser-global keybindings
by moose-technology＠googlecode.com 02 Jul '13

02 Jul '13

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.

1 4

Issue 853 in moose-technology: ConfigurationOfMoose should be split to reflect core vs suite
by moose-technology＠googlecode.com 02 Jul '13

02 Jul '13

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.

1 2

Issue 716 in moose-technology: span or size for each column in GLMTablePresentation
by moose-technology＠googlecode.com 01 Jul '13

01 Jul '13

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.

1 2

Issue 748 in moose-technology: DistributionMap examples not working
by moose-technology＠googlecode.com 30 Jun '13

30 Jun '13

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

1 3

Issue 555 in moose-technology: DSM improve visualization
by moose-technology＠googlecode.com 30 Jun '13

30 Jun '13

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.

1 2

Re: Issue 482 in moose-technology: Use JNIPort to connect to VerveineJ
by moose-technology＠googlecode.com 30 Jun '13

30 Jun '13

Comment #2 on issue 482 by cy.delaunay: Use JNIPort to connect to VerveineJ http://code.google.com/p/moose-technology/issues/detail?id=482 you should now use that: Gofer new url: 'www.squeaksource.com/DelaunayTmpStuffs'; package: 'JNIPort-Initialization'; load. Gofer new url: 'www.squeaksource.com/DelaunayTmpStuffs'; package: 'JNIPortExample'; load. The initialization part still has to be fixed, sometimes it works, sometimes not.

2 4

Re: Issue 432 in moose-technology: Popup should appear only when a certain modifier key is pressed
by moose-technology＠googlecode.com 30 Jun '13

30 Jun '13

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.

1 8

Issue 829 in moose-technology: Roassal Label Text does not scale with Zoom Out
by moose-technology＠googlecode.com 23 Jun '13

23 Jun '13

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.

1 4

← Newer
1
2
3
4
5
6
7
...
14
Older →

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

Moose-dev October 2012