Bug #4819
closed"Column Annotation" view duplicates mappings
0%
Description
If you enter an Annotation using the Column Annotation madlib view, then switch to the table view and select another column, the annotation you just entered will [eventually] appear duplicated in the selected column. This continues as subsequent columns are selected (usually on the second selection event).
I can see where it's happening in the code - and it makes sense that'd it'd be doing that. When the column selection changes, an attempt is made to save the current state of the madlib annotation. I'm just going overboard with what it is actually doing.
I don't want there to be a "save changes" button or anything on that tab, I think it's important that any changes made in that view automatically and immediately persist to the annotation as it exists in memory.
Now I've got to figure out how to have the best of both worlds (save when selection changes, but not in an erroneous way.
Related issues
Updated by ben leinfelder almost 15 years ago
Now "resetting" the madlib annotation tab so that the old values are not saved as a new mapping for the next selected columns.
Funny, this didn't come up for me initially since I was working with a fleshed out annotation example.
Fixed now.
Updated by ben leinfelder almost 15 years ago
I encountered another case where the values from one annotation were populating and saving in another column's.
I changed where the reset() method was called and have not been able to recreate the duplication.
Keeping my eyes open for the problem to resurface since I'm not 100% sure it's fully resolved.
Updated by ben leinfelder over 14 years ago
I should have been editing this bug instead of the bug about overwriting annotations. They were caused by the same issues, and both are resolved at this point.