Jean-Christophe ARNU (JX) wrote:
I use Batik for about 8 month now to display maps. I managed to get what I
wanted to until today. I made a CVS Update of the sources and I recompile
xml-batik and my app with the new jar.
Hi Jean,
Sorry to hear this.
I use a document, which I put ALWAYS_DYNAMIC. The problem is the following :
in the previous version (CVS update also but of august/september), resizing
behaved as usually : my document was resized just like the containter. Now I
did the update (today) resizing does not work and zooming (whereas interactors
are set on a JSVGCanvas) "locks" the maps (zooming with dashed rect) and
others interactors (right mouse button with context sensitive menus) are reset
to act just like left-mouse button coded-behaviour...
It isn't clear to me if you are using Batik's normal behavior here or some
custom code (Batik doesn't really have context menus).
Is there a place I could Track changes around the resize (and more generally
ComponentAdapter/Listener) behaviour changes in the Batik's source?
Well all CVS commits are sent to batik-dev so you can search the
archives. Also you can use the viewCVS interface to browse the changes to
individual source files.
If I have an always_dynamic behaviour, will I have automatically to code a
componentListener to handle Resizing and show/hidden events from the
container?
No as far as I am aware there have been no intentional changes to
how resizing is handled in the default applications. I did do some refactoring
of the code, so it is possible that if you were overriding methods some of
the behavior of those methods has changed (JSVGComponent being the most
likely source of problems). If you are familiur with CVS you can get differences
for entire subtrees (like all of swing).
If you can give me more information on how your application works it might
jog some memories.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
