bgodette wrote:Cause a wazeModel update and that clears. It's indeterminate data from modified segments that's cleared by refreshing the wazeModel (F5/Permalink/Panning far enough/zooming far enough).
When I run into one of those it is usually too late for a reload; I usually have tens of edits unsaved. I simply highlight the segment and set its level properly then keep working. The only viable option (which I never tried) is panning.
Anyway, this never happened to me before, but I'm finding it often now.
BTW, did they fix the problems with segment properties fields in Chrome? Or did I just get used to it?
Sent from my GT-I9100 using Tapatalk 2