Moose-dev

moose-dev@list.inf.unibe.ch

6621 discussions

Issue 824 in moose-technology: Roassal hover text should disappear when dragging node

by moose-technology＠googlecode.com

Status: New Owner: ---- Labels: Type-Defect Priority-Medium New issue 824 by google....(a)ben.coman.com.au: Roassal hover text should disappear when dragging node http://code.google.com/p/moose-technology/issues/detail?id=824 Taking for example ROMondrianExample >> labeledRectangle... Hovering over a node shows a popup with the node text, then moving away from the node makes the popup disappear - which is fine. Hovering over a node shows a popup with the node text, then dragging the node away doesn't close the popup - but I think it should. Additionally, if you drag the node to the popup and leave it there, then moving the mouse away does not close the popup either. Moose47 - ConfigurationOfMondrian.485

12 years, 1 month

Issue 823 in moose-technology: buttons remains after ROMondiranExample >> chooseLayout

by moose-technology＠googlecode.com

Status: New Owner: ---- Labels: Type-Defect Priority-Medium New issue 823 by google....(a)ben.coman.com.au: buttons remains after ROMondiranExample >> chooseLayout http://code.google.com/p/moose-technology/issues/detail?id=823 From Roassal Easel > Example... clicking "chooseLayout" then clicking "Example" doesn't cleanup the buttons from "chooseLayout" Moose47 - ConfigurationOfRoassal.485

12 years, 1 month

Issue 817 in moose-technology: Roassal overwriting window borders

by moose-technology＠googlecode.com

Status: New Owner: ---- Labels: Type-Defect Priority-Medium New issue 817 by google....(a)ben.coman.com.au: Roassal overwriting window borders http://code.google.com/p/moose-technology/issues/detail?id=817 Referring to attached image, you can see on the right hand side the window border is overwritten by graph. This occurs when the window is resized by dragging the bottom right corner. This does not occur when the window is large enough to fully encompass the graph and then inside the graph is moved past the edge of the window. This is with ConfigurationOfRoassal-AlexandreBergel.467 just going World > Tools > Roassal Easel Please fill in the labels with the following information: * Type-Defect, Type-Enhancement, Type-Engineering, Type-Review, Type-Other * Component-XXX Attachments: Roassal-overwriting-window-borders.png 67.8 KB

12 years, 1 month

Re: Issue 813 in moose-technology: Java primitive type "int" created as FamixType

by moose-technology＠googlecode.com

Updates: Labels: Milestone-4.7 Comment #2 on issue 813 by tu...(a)tudorgirba.com: Java primitive type "int" created as FamixType http://code.google.com/p/moose-technology/issues/detail?id=813 (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

12 years, 1 month

Re: Issue 812 in moose-technology: All FamixType are at classScope in MooseChef

by moose-technology＠googlecode.com

Updates: Labels: Component-Famix Milestone-4.7 Comment #3 on issue 812 by tu...(a)tudorgirba.com: All FamixType are at classScope in MooseChef http://code.google.com/p/moose-technology/issues/detail?id=812 (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

12 years, 1 month

Issue 795 in moose-technology: Metrics lcom2 and lcom3

by moose-technology＠googlecode.com

Status: New Owner: ---- Labels: Type-Enhancement Priority-Medium Component-Famix New issue 795 by andreho...(a)gmail.com: Metrics lcom2 and lcom3 http://code.google.com/p/moose-technology/issues/detail?id=795 Moose should have metrics such as lcom2 and lcom3.

12 years, 1 month

Re: Issue 786 in moose-technology: MooseQueryResult>>intersection: is broken

by moose-technology＠googlecode.com

Updates: Labels: Milestone-4.7 Component-Famix Comment #2 on issue 786 by tu...(a)tudorgirba.com: MooseQueryResult>>intersection: is broken http://code.google.com/p/moose-technology/issues/detail?id=786 (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

12 years, 1 month

Issue 784 in moose-technology: opposite is missing in FAMIXLacalVariable>>parentBehaviouralEntity

by moose-technology＠googlecode.com

Status: New Owner: ---- Labels: Type-Defect Priority-Medium New issue 784 by fabrizio...(a)gmail.com: opposite is missing in FAMIXLacalVariable>>parentBehaviouralEntity http://code.google.com/p/moose-technology/issues/detail?id=784 Hi, I figured that parentBehaviouralEntity was implemented like that: FAMIXLacalVariable>>parentBehaviouralEntity <MSEProperty: #parentBehaviouralEntity type: #FAMIXBehaviouralEntity> <MSEComment: 'Behavioural entity declaring this local variable. belongsTo implementation'> ^parentBehaviouralEntity The opposite is missing. Is there a reason for that? Shouldn't it be like: FAMIXLacalVariable>>parentBehaviouralEntity <MSEProperty: #parentBehaviouralEntity type: #FAMIXBehaviouralEntity opposite: #localVariables> <MSEComment: 'Behavioural entity declaring this local variable. belongsTo implementation'> ^parentBehaviouralEntity Cheers, Fabrizio

12 years, 1 month

Issue 720 in moose-technology: Classic Coder should highlight the extension categories

by moose-technology＠googlecode.com

Status: New Owner: tudor.gi...(a)gmail.com Labels: Type-Defect Priority-Medium Component-GlamorousToolkit New issue 720 by tudor.gi...(a)gmail.com: Classic Coder should highlight the extension categories http://code.google.com/p/moose-technology/issues/detail?id=720 Currently, only classes and methods are shown as extensions using gray. Categories should be grayed out as well.

12 years, 1 month

Issue 640 in moose-technology: Get the axis labels in a lineDiagram

by moose-technology＠googlecode.com

Status: New Owner: andreho...(a)gmail.com Labels: Type-Defect Priority-Medium Component-EyeSee New issue 640 by andreho...(a)gmail.com: Get the axis labels in a lineDiagram http://code.google.com/p/moose-technology/issues/detail?id=640 Get the axis labels in a lineDiagram in not working. See example below: | diag factory | factory := ESDummyFactory new. factory yValues: #(22 25 13 16 24 28 35 24 32 24 46 12). factory identifiers: #('January' 'February' 'March' 'April' 'Mai' 'June' 'July' 'August' 'September' 'October' 'November' 'December'). diag := ESDiagramRenderer new. (diag lineDiagram) y: #yValue; width: 500; height: 400; lineWidth: 5; defaultFontSize: 12; identifier: #identifier; labels: [:each | each]; defaultColor: Color blue; yAxisLabel: 'Clients'; regularAxis; deviationValue: 22; deviationDescription: 'avg 2006'; models: factory buildDummies. "startLineAtZero;" ^ diag open

12 years, 1 month

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

Moose-dev