Committed. The code is:
public void keyReleased(KeyEvent e)
{
if (e.getKeyCode() == KeyEvent.VK_BACK_SPACE)
{
if (coordinates.size() > 1)
coordinates.remove(coordinates.size() - 1);
panel.repaint();
Larry,
Kudos for your work on improving rendering performance in OpenJUMP.
Should we test the fix you mention where we "rough clip" large
lineStrings that contain the viewport in their bounding box?
The Sunburned Surveyor
On Mon, Feb 22, 2010 at 3:04 PM, Larry Becker wrote:
> If the problem is
I'm waiting on Stefan's magic 1000 point polygon. Mine draws too quickly to
benchmark.
On Tue, Feb 23, 2010 at 10:08 AM, Sunburned Surveyor <
sunburned.surve...@gmail.com> wrote:
> Larry,
>
> Kudos for your work on improving rendering performance in OpenJUMP.
> Should we test the fix you mention
Hi!
I tested the new mouse wheel zoom with the nightly build from 23-Feb-2010
02:12.
(A) In previous versions the zoom function zoomed-in to the current position
of the mouse cursor. The new behavour is, that it just zooms to the position
in middle of the layerviewpanel. I'd like to have the old
thanks again
Larry Becker wrote:
> Committed. The code is:
>
> public void keyReleased(KeyEvent e)
> {
> if (e.getKeyCode() == KeyEvent.VK_BACK_SPACE)
> {
> if (coordinates.size() > 1)
> coordinates.remove(coordinates.si
Hi Benjamin,
(A) I like the old zoom to mouse position behavior too. I just haven't
gotten the zoom to cursor math right yet.
(B) You might be right. I've noticed an occasional anomaly too, but can't
reproduce it consistently. I don't know what is causing it.
regards,
Larry
On Tue, Feb 2
Hi *,
first of all thanks to Larry for correcting and commiting my previous request!
so here is my second "Request". I would like to "open" the SplitLineStringsOp
to get easier access to its internals where needed ( atleast the split-method ).
One way would be to overwrite the SplitLineString
