[udig-devel] Three misc. questions

[Jody Garnett]

David Fleig wrote:
> 1. I have added layers to draw additional information as pulled from a
> database onto the map. The initial rendering seems to work fine. However, if
> something changes and I need to update the given information not everything
> seems to show up properly. I have tried two approach of just modifying the
> layer to add/remove elements and entirely removing the layer and adding it
> fresh. Sometimes the new features will show up, sometimes they won't. I have
> noticed that they will show up at certain scaling distances, but it appears
> somewhat random.
>   
That is confusing; the idea was to use DataStore events to notify the 
renderer when (and where) the screen
needed to be redrawn.
>
>
> 2. When creating your own layers/feature stores/features...(I'm just using
> an in memory collection) If a user makes changes (say moves a feature), when
> they choose 'commit' what does this call back into? Something in the feature
> store perhaps that I could push back into the application?
>   
There is a "Transaction" with commit() and rollback() methods - this is 
used to keep all the datastores in sync
(in case you were editing more then one).
>
> 3. Is it possible to change the default behavior of "info", either by an
> extension point or other mechanism so that instead of the generic property
> view of that feature appearing, something else is shown?
>   
Hi David;

We have a policy of not introducing extension points until someone asks. 
So if this is indeed the request
we can certainly do it. It will not take long - the code is designed 
with this in mind (with interfaces and so on).

One thing I would like to be sure of is if *you* are available to do QA 
on the new extension point. That is can you
try implementing the new extension point and give us feedback on the 
documentation & examples.

Jody