Hi Andre,
> I open several shape files contains points, lines, and polygons. Then
> I tried to edit my polygons by using the "create cookie cut" and "auto
> complete polygon". I opened the same shapefiles with v2721 and 2851.
> I notice that there is a delay in 2851 longer than 2721 when I do
> editing to my shapefiles. because everytime after i click my mouse to
> end the editing, i have to wait longer (i feel that it is not more
> than a second, probably wrong)
I could not measure this slowdown.
To test it, I used a shapefile with overcomplicated polygons and tried
both tools
"create cookie cut" and "auto complete polygon" on the same object.
It lasted more than 5 s in both cases (no difference easily measurable).
Note that the speed of these tools are probably dependent on
1) polygon complexity (overlay calculation on this polygon)
2) shapefile size (screen refresh at the end of operation)
3) total amount of loaded data compared with max memory available
(garbage collection activity is higher and pauses are more frequent if
you're near the max)
Micha�l
>
> This delay was not counted by clock, but I can feel it, that after i
> press the mouse, i have to wait a little bit longer (momentary lag).
> It is correct that even the 2721 has this momentary lag, but the 2851
> gives a little bit longer.
> I dont think the operating system cause it since i use the same
> computer. I am using windows 7 with 6.31 java.
>
> I think this delay is not really important, because its based on my
> feeling rather than counting the clock.
> i am still happy using it, especially with the faster start up.
>
> thank you for the improvement.
>
>
>> From:
edgar....@web.de
>> Date: May 06 04:17PM +0200
>> Url:
http://groups.google.com/group/openjump-users/msg/9a613531c0e024ed
>>
>> How do measure editing speed or even notice the difference of less than a
>> second?
>>
>> In case that's not due to momentary lags in your operating system, meaning
>> consistently reproducible when running both revisions multiple times, could
>> you give us a step by step routine to reproduce it?
>>
>> If it's a problem it was most likely introduced before 2851 as the changes
>> in the PluginManager most likely won't affect usage performance in any way
>> except of breaking some extension completely ;).
>>
>> thanks for the reply and come back with more details if your issue persists
>> in newer versions. ..ede
>>
>>