Latest issues

This should not belong to the layout I have the impression. Where to position the camera against the nodes the view contains is the real question in my opinion. Probably that the other layout are not doing it in the right way. I have added ROFocusView class>>centerView: The Mondrian builder has been updated accordingly. For example: -=-=-=-=-=-=-=-=-= view nodes: (Collection withAllSubclasses). view edgesFrom: #superclass. view radialTreeLayout. view center. -=-=-=-=-=-=-=-=-= produces what is expected. In Roassal 1.356. Doru, if you agree with this, then close the issue. Status: Started

Try this: view nodes: (Collection withAllSubclasses). view edgesFrom: #superclass. view radialTreeLayout. The center of the graph is placed at 0@0, and this is annoying because you do not see half of the graph. The layout should translate the graph to make it start at 0@0

It should be available in the next build Status: Fixed

Good point. We should update the installation scripts. If you want, you can take a look at MooseImageSetupCommandLineHandler>>installLogo Labels: Component-Finder Milestone-4.8

Thanks. Status: Invalid

I've downloaded Moose 4.8 image (rather than the Gopher I used before). This shows the Moose logo on the desktop. Could I suggest the Moose logo should be configurable to be shown / not shown using: Settings Browser / Appearance / Desktop / Show logo...

Please close this error. It has nothing to do with Moose. It is something specfic to my mounting USB drives. I can reproduce this error from the (Pharo) Systems Settings if I try to select a new (Pharo) Desktop Background image file name. If I mount a USB memory card as a new drive, the pop-up doesn't occur there, but ==does== occur later in selecting a fil, if I try to select a file on a different drive. This error now occurs where I successfully changed the desktop background before (same image). Maybe I removed a USB without dismounting. I have downloaded a new Pharo VM (no Moose), and I get the same issue.

I thought we addressed this, but actually no. I have just fixed this problem. Doiting the code Usman gave is really fast in version 1.344 of Roassal Status: FixedLabels: -Priority-Medium Priority-High

hi Ben, your code is indeed part of Roassal. I have the impression however that we do not fully exploit the possibilities of this. I fix this. Status: Fixed

I'm not sure. I think I remember Alex integrating my contribution for CTRL and SHIFT key modifiers to do the multiple selection, but there is no record here, and its too long ago (wow! has it been that long). As far as I know the issue of resetting the selection to empty by clicking on the background (point 1. above) has not been addressed. I think the multiple-selection would be a really good feature for Roassal, however... * I haven't been very attentive to it. I plan to have it in my application but its on the backburner until I finish a few other things. * I think Roassal has moved on a lot since then, so I'm not sure how much love it will need now. So perhaps for now it should be closed again. Once I get my dissertation submitted, I plan to move my application to latest Moose. Then this will probably arise again, but I can open a new issue at that time once I have something more definite and time to assist.

What is the status here?

I also fixed a couple of things there. Now, it should be fine. Status: FixedLabels: Milestone-4.8

Status: WontFix

Is this still an issue?

I cannot reproduce that. I am using Moose daily on Windows 7 and this never happened. Do you happen to have anything named Harddisk3 in your machine?

After opening the Moose Panel, clicking on the Import Model from MSE file icon (marked MSE) up pops a windows (not Pharo) error message (attached). Although I am running Windows (Win 7), this looks like a Linux or Mac mount point. Does anyone have any idea what is happening? Problem is not fatal, as when I select cancel it goes on perfectly well to display the directories and files and allows me to select a MSE file, but it is a pain.

Please remove the code. It should use inFamix anyway, but we can add it at a later time. Labels: Component-MooseCore Milestone-4.8

Is this class used by anybody? Apparently it imports Java model using infusion may be. There is no test on it. It is buggy on pharo 2.0 (uses old FileDirectory) ...

I think the problem lies in the theme you are using. Could you try to: - execute GLMUITheme defaultSettings: nil. GLMUITheme beCurrent. - check again ?

More information - this only error occurs when the Entity is filtered on a tag. This error does not occur when the Entity is not filtered on a tag. This error does not occur when the Entity is already displayed within the filering (see attached PharoScreenshot3.png) In the attached example, I have first clicked on the Dude tag to filter on the flag, then on FAMIX.Type in the Map. As you can see (attached as PharoScreenshot.png), the Entity panel does not expand or remove the filtering to show the selected FAMIX.Type Yes - hard to say if this is incorrect behaviour or not. Just unexpected on my part.