Angus Leeming <[EMAIL PROTECTED]> writes:
| Next question. Just beneath this last statement in the UserGuide we have:
|
| Notice that if you revert back all changes to arrive to the document as it
| was last saved, the "changed" status of the document is unfortunately not
| reset. This is a known bug.
It is a bug...
| I guess that this is a consequence of the above, no? We can't apply the
| following fix, because the limit means that changes will be popped off the
| stack.
|
| case LFUN_UNDO:
| disable = buf->undostack.empty();
| + if (disable)
| + buf->markLyxClean();
| break;
This patch would be wrong anyway...
To do anything else we would have to store the status in the undo
information, but only act upon it if there were no other undo objects
belonging to the same buffer.
And later when we have a "pick the undo you want to apply now" this
will be interesting.
That said I think we should support clearing of the changed flag if we
are sure about the state, but we are not there yet.
| Is my reasoning correct here? I'll modify the documentation to
| reflect this.
I don't think you are far off...
Lgb
