Closed totikom closed 1 year ago
this fix the issue, mentioned in #1867. The bug was caused by the order, in which Widget::set_values and Widget::set_format methods were called.
Widget::set_values
Widget::set_format
By the way, semantics of Widget::set_values is very unintuitive: it sets new values for State::Format case and silently does nothing on other cases.
State::Format
Should I create a PR, which will change this behavior to something more intuitive?
I think I fixed this in 55e9334 by allowing .set_values() before .set_format(), can you verify please?
.set_values()
.set_format()
Yep, I'll check it. If it fixes the issue, I'll change #1877 so it will not depend on my fix.
this fix the issue, mentioned in #1867. The bug was caused by the order, in which
Widget::set_values
andWidget::set_format
methods were called.By the way, semantics of
Widget::set_values
is very unintuitive: it sets new values forState::Format
case and silently does nothing on other cases.Should I create a PR, which will change this behavior to something more intuitive?