It could very well happen. See issue: http://code.google.com/p/moose-technology/issues/detail?id=112
It would be helpful if you could check by inspecting the graph.
Cheers, Doru
On 26 Jan 2010, at 15:22, Laval Jannik wrote:
Hi Alex,
In DSM, I have a problem with edges: they do not appear since version 350 of Mondrian. I wonder if they are not below shapes.
Cheers, Jannik
On Jan 26, 2010, at 15:01 , Alexandre Bergel wrote:
Color problems are probably not related to my fixes. What is going wrong with DSM beside the colors? Best would be to write some tests that fails. This will give me a starting point where to start.
Cheers, Alexandre
On 26 Jan 2010, at 10:31, Simon Denier wrote:
That's cool
Jannik is checking the changes because DSM does not work completely.
I also noticed a strange thing with colors.
Open a cycletable like MOCycleTable new cycles: (MOCycleTableTest new setUp); render
Notice how the fill color is desaturated (alpha: 0.5) in the two cells. Now if you fly over the cells with the mouse, the color is fully saturated once redrawn. Any idea where this comes from?
<Screen shot 2010-01-26 at 14.30.31.png>
On 25 janv. 2010, at 20:27, Alexandre Bergel wrote:
Dear List,
You will find below the health report of today. I removed two important bottlenecks: node translations and computing absolute bounds. Layouting nodes is more then 100 times faster! You can now do a "view nodes: (1 to: 20000)" in an easel without having the time to take a coffee!
Here is the comment of Mondrian-Alexandre_Bergel.352
Major speed improvement:
- MOGraphElement>>absoluteBounds uses now a cache. This helped
speeding up Mondrian by 35%
- Make MORectangleShape>>display:on: use absoluteBounds instead
of absoluteBoundsFor:, which speeded the UI up of 14%
- optimization when translating nodes
(MOGraphElement>>translatedBy:), we gained a significant speedup when layouting nodes -=-=-=-=-=-=-=-=-=-=-=-=
Report produced on 2010-01-23T18:17:13+00:00 Benchmark ManyNode (simple rendering of nodes) : 100 nodes => 3 ms 200 nodes => 5 ms 300 nodes => 6 ms 400 nodes => 7 ms 500 nodes => 9 ms 600 nodes => 10 ms 700 nodes => 12 ms 800 nodes => 14 ms 900 nodes => 15 ms 1000 nodes => 17 ms 1600 nodes => 28 ms Benchmark ManyEdges (simple rendering of edges) : 10 edges => 2 ms 20 edges => 6 ms 30 edges => 12 ms 40 edges => 28 ms 50 edges => 48 ms 60 edges => 74 ms 70 edges => 115 ms 80 edges => 169 ms 90 edges => 254 ms 100 edges => 335 ms 200 edges => 4356 ms 300 edges => 35919 ms 55.54 % of methods are covered Progress from last time: -0.1 %
Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- Simon
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- www.tudorgirba.com
"Every thing has its own flow."