uDIG

Layer bounds remember old bounds even if it was reduced by deleting features

Details

Description

The problem is evident when using the Zoom to Layers button of the layers view.
Tested with PostGis Layers, not sure if the same happens with other kinds.
To reproduce:

  • Zoom out a considerable amount so the current layer occupies a small area in the map
  • Add a feature that is far away from the rest of features in the layer
  • Commit
  • Delete the just added feature
  • Commit
  • Zoom to Layer zooms to the extent including the just deleted feature. That is, a far longer area than the actual one.

By restarting uDig the problem disappears. So it might be some kind of cached extent not being updated.

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Jesse Eichar added a comment -
Yes :). So the root problem is the design of the catalog makes the resources and services read only. So they cannot be updated externally. Although now that I think about it it may not be such a problem. Here's a solution that I partially implemented for MemoryDatastore.

MemoryDatastore adds a listener to the datastore when it is created (or rather when the info is created) and everytime an even comes in it recalculates its cache. What we need to do is create a super class for all Datastore IServices and IGeoResources that handles all of this sort of shared code. RIght now there is a horrendous amount of duplication between IServices and IGeoResources.
Show
Jesse Eichar added a comment - Yes :). So the root problem is the design of the catalog makes the resources and services read only. So they cannot be updated externally. Although now that I think about it it may not be such a problem. Here's a solution that I partially implemented for MemoryDatastore. MemoryDatastore adds a listener to the datastore when it is created (or rather when the info is created) and everytime an even comes in it recalculates its cache. What we need to do is create a super class for all Datastore IServices and IGeoResources that handles all of this sort of shared code. RIght now there is a horrendous amount of duplication between IServices and IGeoResources.
Hide
Permalink
Jody Garnett added a comment -
So where was your solution Jesse?
Show
Jody Garnett added a comment - So where was your solution Jesse?

People

  • Assignee:
    Unassigned
    Reporter:
    Gabriel Roldan
Vote (0)
Watch (0)

Dates

  • Created:
    Updated: