14 Aug
2010
14 Aug
'10
5:31 p.m.
Alex, I was generating a graph in which I wanted the
edges to
have a width computed based on some property. The block
that I passed to width: was slow and was throwing an
exception. Since it was slow, the image would freeze
while computing all the widths of all the edges in the view,
and since the exceptions were not thrown I was waiting ...
Yes, this was the behavior in previous versions of Mondrian
Now the problem is fixed. I will update to the latest
version
of Mondrian nevertheless and see how it behaves.
You should not get this problem anymore.
Cheers,
Alexandre
On Sat, Aug 14, 2010 at 12:26 AM, Alexandre Bergel <alexandre(a)bergel.eu> wrote:
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
More or
less, but use at your own risk, because exception in Mondrian have been known to freeze
the image or raise a huge amount of pop-up (due to being in the UI thread)
I think there are three places where to start when dealing with exceptions in Mondrian:
MOGraphElement>>handleException: (calls haltOnce)
It has no sender. I recently remove all sender of it since the visualization is first
rendered in a non displayed form. A debugger will popup on error
MOBoundedShape>>display:on: (this is the
one which gives a red shape in case of error)
This is not necessary anymore. The last version of Mondrian removed this particular
case.
MOCanvas>>raiseError:
This is also cleaned.
Mircea, what do you want to achieve?
Cheers,
Alexandre
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
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