view shape rectangle size: 20.
view interaction action: #inspect.
view interaction
whenEnteringUpdateNode: [:node | view interaction forwarder.
view nodes: (Set allSubclasses).
view interaction forwarder.
view edgesFrom: #superclass.
view treeLayout ]
whenLeavingUpdateNode: [:node | ] withLayoutUpdate: true.
view nodes: (1 to: 3)
when I try this example I do not see the tree representing subclasses.
Stef
Hi Tudor. I have no idea about Moose, but I was wondering if you need to
copy models (in addition to export them to disk).
So, do you need? and if true, how do you do it? #veryDeepCopy ?
Thanks
--
Mariano
http://marianopeck.wordpress.com
Status: Accepted
Owner: damien.c...(a)gmail.com
CC: tudor.gi...(a)gmail.com
Labels: Type-Defect Priority-Medium Component-Glamour
New issue 631 by damien.c...(a)gmail.com:
GLMListMorphicTest>>testOnlyOneMorphPerRowInList failing
http://code.google.com/p/moose-technology/issues/detail?id=631
The test GLMListMorphicTest>>testOnlyOneMorphPerRowInList is failing. It
looks like the node 43 is always the one which makes the last assertion
fail.
We should try to reproduce outside the Glamour environment.
Hi Cyrille,
Thanks for fixing the VerveineJ wizard.
It would indeed be cool to get the variables set in the settings.
One idea would be to have as default folder for VerveineJ as relative to the current moose.image. Like this we could just copy VerveineJ in the current folder (and package it in the Moose Suite one click) and everything would just work.
Cheers,
Doru
--
www.tudorgirba.com
"Not knowing how to do something is not an argument for how it cannot be done."
Scenario one:
bookmark a model
(I did not know what is should do)
this creates a tab with a x cross
I clicked on it
argh I lost my model
but the model is still in the list
argh I click and I get a DNU.
Stef (next bug soon :).
Because we did it for
http://www.themoosebook.org/book/externals/import-export/root-folder
kind of ....
I suggested to cyrille to spend 1 hours and add some settings.
Which ones do you want to have.
Me
- Project main folder location
- VerveineJ code location
- Import statements to be used
I do not see why I have to type
PATH_TO_verveine.extractor.java/verveine.sh -Xmx 2000m -- .
Each time I import a model I do not want to have to dive into this fucking file system to find my way (with a soon) resizeable interface.
Stef