search

EcoGIS / CAPS-Scenario-Builder

The CAPS Scenario Builder will allow government officials, conservation groups and others to submit "scenarios" for proposed changes to land cover and infrastructure so that these changes can be assessed for their impact on ecological integrity.
http://www.umass.edu/landeco/research/caps/caps.html
3 stars 0 forks source link

Issue: When loading a saved scenario, not all edit layers that were previously are loaded #6

Closed ghost closed 12 years ago

ghost commented 12 years ago

Win 7 SP 1 - When I edit a scenario, save it, exit, and reload, not all edit layers are reloaded (polys weren't). When I export the scenario, the unloaded layers don't get exported.

ghost commented 12 years ago

Clarification: the editing layers were indeed saved, they just didn't get automatically loaded when I loaded the saved scenario, though they'd been there when I saved it.

bobenglish commented 12 years ago

I was unable to duplicate the layer not reopening behavior for polygon layers. As I think I mentioned before, if you save a scenario, then load a new editing layer and save edits but choose to discard the scenario then the editing layer you opened after the last time you saved the scenario will be deleted.

If you can, try to give me specific steps to repeat this bug. If not, I will look carefully at the code for errors that could cause this behavior.

ghost commented 12 years ago

As with the other 2 nasty bugs I've hit, I haven't been able to reproduce this. I suspect that I did something to cause the first one, and it corrupted the dataset to cause the second two.

bobenglish commented 12 years ago

I'll look at it carefully when I debug and test.

bobenglish commented 12 years ago

I refactored the save scenario and save scenario as... methods and went over them with a fine tooth comb. I also tested saving some edit layers and then discarding others. Everything looks like it works fine now. I have fixed at least one bug (Scott's missing base_towns layer) that easily could have caused this behavior. I'm going to close this now, but I will keep my eyes open for any behavior like this when I'm doing the phase II testing.