Summary: | okteta does not set document as modified when it is changed | ||
---|---|---|---|
Product: | [Applications] okteta | Reporter: | esigra |
Component: | general | Assignee: | Friedrich W. H. Kossebau <kossebau> |
Status: | RESOLVED FIXED | ||
Severity: | normal | ||
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Gentoo Packages | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: |
Description
esigra
2009-11-09 18:07:56 UTC
Indeed, thanks for your report. This happens even in the current development version. Will investigate. SVN commit 1046919 by kossebau: backport of 1046918: fixed: doing some grouped change (e.g. editing values, which is one behind the scenes) if unmodified does not emit the modifiedChanged signal CCBUG: 213868 M +2 -0 piecetablebytearraymodel_p.cpp WebSVN link: http://websvn.kde.org/?view=rev&revision=1046919 SVN commit 1046929 by kossebau: backport of 1046927: fixed: logic was inverted, canClose should be true if a modified document was successfully synced BUG: 213868 M +2 -2 kdocumentsyncmanager.cpp WebSVN link: http://websvn.kde.org/?view=rev&revision=1046929 Hm, were two bugs residing there since the early days of Okteta, the later even loosing data if the save failed as the inverted logic resulted in closing the document, ouch. Thanks a lot for being the one finally reporting them :) Fixes should be coming with KDE 4.3.4 and 4.4.0 |