Updates:
Labels: -Milestone-4.2
Comment #4 on issue 228 by tudor.gi...(a)gmail.com: Nested browsers do not
take "when", or "display" into account
http://code.google.com/p/moose-technology/issues/detail?id=228
(No comment was entered for this change.)
Status: New
Owner: ----
Labels: Type-Defect Priority-Medium
New issue 1056 by v.blonde...(a)gmail.com: Can't export as PNG with Roassal
export button
http://code.google.com/p/moose-technology/issues/detail?id=1056
Describe the problem: what do you get? what do you expect?
When you add the export button, on a Roassal view and you select PNG
export, you get:
MessageNotUnderstood: ROAthensImageExporter class>>subclassRespondibility
How to reproduce the problem: step by step if necessary
ROMondrianViewBuilder new exportButton ; open.
Clic on Export and Export as PNG.
Additional information: platform, context which may impact the problem
Moose 5.0 - W7
Please fill in the labels with the following information:
* Type-Defect
* Component-Roassal
--
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
Updates:
Summary: Roassal does not export the full PNG / SVG
Comment #6 on issue 995 by tu...(a)tudorgirba.com: Roassal does not export
the full PNG / SVG
http://code.google.com/p/moose-technology/issues/detail?id=995
(No comment was entered for this change.)
--
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 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