uDIG
  1. uDIG
  2. UDIG-1209

Commit and Rollback buttons always enabled

    Details

      Activity

      Hide
      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
      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
      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
      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
        • Votes:
          1 Vote for this issue
          Watchers:
          1 Start watching this issue

          Dates

          • Created:
            Updated: