Status: New
Owner: ----
Labels: Type-Defect Priority-Medium
New issue 1067 by james.fo...(a)gemtalksystems.com: MoosePanel panes showing
group should be sorted
http://code.google.com/p/moose-technology/issues/detail?id=1067
I can resort them by executing a Smalltalk expression, but the default
order should be meaningful rather than random.
* Type-Enhancement
* Component-MoosePanel
--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings
Status: New
Owner: ----
Labels: Type-Defect Priority-Medium
New issue 1069 by v.blonde...(a)gmail.com: Use self notExistentMetricValue
instead of -1 in some metrics of MooseEntities
http://code.google.com/p/moose-technology/issues/detail?id=1069
Describe the problem: what do you get? what do you expect?
FAMIXBehaviouralEntity, FAMIXType, FAMIXFileAnchor and
FAMIXSourceTextAnchor define metrics where -1 is used instead of self
notExistentMetricValue.
Additional information: platform, context which may impact the problem
Moose 5.0
Please fill in the labels with the following information:
* Type-Enhancement
* Component-Moose-Core
--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings
Status: New
Owner: ----
Labels: Type-Defect Priority-Medium
New issue 1080 by v.blonde...(a)gmail.com: DNU when inspect FAMIXClass new
http://code.google.com/p/moose-technology/issues/detail?id=1080
Describe the problem: what do you get? what do you expect?
Try to inspect:
FAMIXClass new
You get : DNU receiver of "sourceLanguage" is Nil
This DNU is thrown by the glamour visualisation.
IMHO, This error should be catched by glamour and shown after in the
inspector.
How to reproduce the problem: step by step if necessary
FAMIXClass new
Additional information: platform, context which may impact the problem
W7 - Moose latest
Please fill in the labels with the following information:
* Type-Defect, Type-Enhancement
* Component-Glamour
--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings
Status: New
Owner: ----
Labels: Type-Defect Priority-Medium
New issue 1071 by leo.per...(a)gmail.com: font size in playground
http://code.google.com/p/moose-technology/issues/detail?id=1071
When I change the size of the source code font in the settings it does not
have any impact in the playground on the last image (06/04/2014).
I'm on Ubuntu 13.10
--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings
Status: New
Owner: ----
Labels: Type-Defect Priority-Medium
New issue 1081 by usman.bh...(a)gmail.com: debugger is broken
http://code.google.com/p/moose-technology/issues/detail?id=1081
Do, for example, 1 add: 1 in a playground and we get a debugger window with
an execution stack. The problem is that when clicking on an item in the
stack, nothing happens. So debugging is currently broken.
--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings
It seems that GLMTabulator when creating rows, does not take into account
size of the container into which rows are placed. The bottom row surpasses
the size of its container by the amount of the size specified for the top
row and it is not completely visible. Here is a script that shows the
problem.
|tab|
tab := GLMTabulator new.
tab column: [ :col |
col
row: #first size: 80;
row: #second;
row: #third size: 100].
tab transmit to: #first; andShow: [:a | a dropDownList display: [:x | 1 to:
x ] ].
tab transmit to: #second; andShow: [:a | a list display: [:x | 1 to: x ]
].tab transmit to: #third; andShow: [:a | a list display: [:x | 1 to: x ] ].
tab openOn: 10
I know the specifying size as span shows correctly the tree rows but then
droplistMorph get resized awkwardly, and size works better for the widget.
Is this a known issue?
usman
[image: Inline image 2]
Status: New
Owner: ----
Labels: Type-Defect Priority-Medium
New issue 1039 by ssadams....(a)gmail.com: Glamour layout clipping bug
http://code.google.com/p/moose-technology/issues/detail?id=1039
When sizing a presentation row, I noticed the bottom pane extends below the
top window bounds and is clipped.
browser := GLMTabulator new.
browser row:#textField size:30;
row: #listField.
browser transmit to:#textField; andShow:[:a| a text
display:[:x| 'Hello Doru!']].
browser transmit to:#listField; andShow:[:a| a list
display:[:x| 1to:200]].
browser openOn: 123
Additional information: platform, context which may impact the problem
Pharo 2.0
ConfigurationOfGlamour-TudorGirba.123
* Type-Defect
* Component-Glamour
--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings
Status: New
Owner: ----
Labels: Type-Defect Priority-Medium
New issue 1083 by chisvasi...(a)gmail.com: Wrong offset when rendering a
GLMTabulator
http://code.google.com/p/moose-technology/issues/detail?id=1083
The renderer of a GLMTabulator does not properly compute the offset of a
column/row if a column/row contains at the end multiple panes with a fixed
size:
|tab|
tab := GLMTabulator new.
tab
row: #first size: 100;
row: #second;
row: #third size: 100;
row: #forth size: 100.
tab transmit to: #first; andShow: [:a | a list display: [:x | 1 to: x ] ].
tab transmit to: #second; andShow: [:a | a list display: [:x | 1 to: x ] ].
tab transmit to: #third; andShow: [:a | a list display: [:x | 1 to: x ] ].
tab transmit to: #forth; andShow: [:a | a list display: [:x | 1 to: x ] ].
tab openOn: 10
--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings