uDIG

Commit and Rollback buttons always enabled

Details

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Jody Garnett added a comment -
Is this still the case? We can tell when a transaction has been used so we should be able to get this one....
Show
Jody Garnett added a comment - Is this still the case? We can tell when a transaction has been used so we should be able to get this one....
Hide
Permalink
John Hudson added a comment -
This is still an issue: rollback and commit buttons still always enabled.
Show
John Hudson added a comment - This is still an issue: rollback and commit buttons still always enabled.
Hide
Permalink
Silvia Franceschi added a comment -
Confermed, the two buttons are always enabled.
Show
Silvia Franceschi added a comment - Confermed, the two buttons are always enabled.
Hide
Permalink
Jody Garnett added a comment -
There are facilities in the EditManager to recognize with a DataStore is requested; or perhaps even when one of the write methods are used; and enable the buttons at that time.

We had some problems (because FeatureSource does not have a setTransaction method) with using a FeatureSource for rendering; while editing with a FeatureStore and having the map out of sync. We "solved" them by requesting a FeatureStore first (ie all the time) and that is probably throwing the button enablement off.

We should be able to look at the BasicFeatureRenderer and turn off this "fix" now that we have some time. We can also go about adding featureSource.setTransaction - if it has not been done already.
Show
Jody Garnett added a comment - There are facilities in the EditManager to recognize with a DataStore is requested; or perhaps even when one of the write methods are used; and enable the buttons at that time. We had some problems (because FeatureSource does not have a setTransaction method) with using a FeatureSource for rendering; while editing with a FeatureStore and having the map out of sync. We "solved" them by requesting a FeatureStore first (ie all the time) and that is probably throwing the button enablement off. We should be able to look at the BasicFeatureRenderer and turn off this "fix" now that we have some time. We can also go about adding featureSource.setTransaction - if it has not been done already.

People

  • Assignee:
    Unassigned
    Reporter:
    Jesse Eichar
Vote (1)
Watch (1)

Dates

  • Created:
    Updated: