Sean Hanlon wrote:
>
> I tried
> removing the CardLayout and, on user selection, add the JSVGCanvas to the
> panel directly (so on resizes only the currently visible canvas is
> resized).
> The problem I saw with this approach is that the JSVGCanvas wasn't scaled
> and didn't maximize the display area as it does when I load them all at
> initialization in the CardLayout.
>
>
Guess you need to try and see how the initialisation of a JSVGCanvas within
CardLayout is different when compared with initialising JSVGCanvas outside
of it as you had attempted.
Maybe CardLayout is registered with the Java windowing system so gets
notified of a resize/maximise, and, when a JSVGCanvas is not initialised
within it then it doesnt know that it should maximise. Try to check if your
JSVGCanvas's are correctly hooked up to be made aware of any such events at
the appropriate time.
If it were me I'd be stepping through the batik source on Eclipse debugger
to see what happens.
Another thought is, does it matter, if you can resolve it by increasing the
heap. Memory is quite cheap. I'd be more concerned about how fast it ran
than memory usage. How much more do you need to increase the heap by? A lot?
Or a little?
--
View this message in context:
http://www.nabble.com/Using-multiple-JSVGCanvas%27-in-a-CardLayout---Heap-Overflow-tp17018867p17021573.html
Sent from the Batik - Users mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
