This conversation is a continuation from the Get Satisfaction forum. See old posts here: https://getsatisfaction.com/antetype/topics/this_widget_is_changing_states_on_a_breakpoint_despite_not_having_a_breakpoint_state#reply_14502500
just a minute ago we released a new 1.6 beta which should fix this bug. While converting a document it checks for files created in 1.5 beta and converts them.
Thanks Al, makes sense.
Hi Ben the next beta will have a fix that ignores these invalid states that were created in the early 1.5 beta. You should no longer see the Default- (null) in the style bar.
Selection from the context menu, style bar or style inspector will always be a valid state and you will no longer see the states in the specification screen.
If you still have documents that have items with these invalid states selected (and therefore see default - (null) in the style bar) - please change state to a valid state and you will no longer have a way to select the invalid states again.
I hope this makes sense and eradicates any further errors for you.