Buffering a selected set a 2nd time does not work

[andersd]

This happens in the trunk demo 'http://www.geomoose.org/demo/geomoose.html' using IE8, FireFox11, and Chrome.

1. Select features
2. Buffer 10 feet using "Buffer these results"
3. This creates a new select set.
4. Press "Buffer these results"

Problem - nothing happens
Work Around Fix - Select features again with mouse.

[theduckylittle]

This is current "Working". It does now change the appropriate selection radius, however, it always refers back to the original buffer set.

[andersd]

This is still not working. Also check ticket 89 for other buffer issues.

1. Select a pareclt (select features or search parcels)
2. Buffer 10 feet (works great)
3. Buffer results 10 feet <-- Problem buffer does not work - Click button and nothing happens.

[EliL]

I think 'Buffer these results' should do one of the following:

1. buffer the current selection (not the original selection)
2. Return the 'Buffer these results' results with a different html header that does not contain the 'Buffer these results' link (i.e. a user is not given the opportunity to buffer selection sets multiple times).

[theduckylittle]

I added a fix to drop/hide the "Buffer these results" once a second buffer distance has been specified. The buffer distance can be changed with "Back to Settings."

r801

[EliL]

There is no longer a UI issue in that this no longer displays "Buffer these results" a second time which does not do anything (i.e. comment option 2 was implemented). Whether it should in the future do recursive buffering I'll leave for someone else to comment on.

[andersd]

When you go "back to settings" and change buffer it only buffers the original set. So this lets you in effect redo your buffer search. It is buffering the new set (see Eli's comment above'). So.. are removing the capability of doing recursive buffering?

[theduckylittle]

We never had recursive buffering. So, essentially, we just clarified the UI a substantial amount. And the "back to settings" is properly allowing the user to change their buffer setting.

IMO this is fixed. If someone has a different opinion they can re-open the ticket.