26 Jun
2010
26 Jun
'10
12:13 a.m.
Thanks, Alex.
It works.
Cheers,
Doru
On 26 Jun 2010, at 00:11, Alexandre Bergel wrote:
The problem is fixed. Version 481 contains a test that
shows the
problem and a fix for it.
Cheers,
Alexandre
On 25 Jun 2010, at 07:11, Laval Jannik wrote:
--
www.tudorgirba.com
"What we can governs what we wish."
Hi Doru,
I confirm the problem.
I tried to use blueprint yesterday, without success.
Cheers,
Jannik
On Jun 25, 2010, at 00:20 , Tudor Girba wrote:
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev Hi,
With the recent changes in Mondrian it looks like the class
blueprint is broken. The problem seems to be due to incorrect
bounds of the parent node. I noticed when by spawning the
blueprint of a hierarchy of classes, I got overlapping classes.
I will take a closer look, but it would be great if someone could
confirm this problem. I guess it should happen with other nested
visualizations.
Cheers,
Doru
--
www.tudorgirba.com
"Reasonable is what we are accustomed with."
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
---
Jannik Laval
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev