Here is an example:
|t|
t:=TextModel new.
t text:'hello'.
t openWithSpec.
t hasUnacceptedEdits
it shows that our text has unaccepted edits, although the
text did not change. ( and there is actually no text decoration
indicating this state).
I tried to follow the trace from #openWithSpec to the call
that sets #hasUnacceptedEdits:true.
I don't think this is a problem of "initialization is
difficult" but a problem of pluging rubric text components as
widgets for spec.
The way spec-models are working and the way rubric works,
just don't fit well.
(see issue
16873Adding a new Method marks current entry in SendersOf
MessageBrowser as dirty
for another example. The cause is that rubric somehow changes
this "hasUnacceptedEdits state" when the text actually *did not
change*. And this
again is difficult to trace down. And I don't know how to fix
this.
Help appreciate