Bug 90933

Summary: "START" and "NUM" in KST file attached to ELOG request
Product: [Applications] kst Reporter: Marc-Antoine Miville-Deschenes <mamd>
Component: generalAssignee: Andrew Walker <arwalker>
Status: RESOLVED FIXED    
Severity: wishlist    
Priority: NOR    
Version: 1.x   
Target Milestone: ---   
Platform: Fink Packages   
OS: Other   
Latest Commit: Version Fixed In:

Description Marc-Antoine Miville-Deschenes 2004-10-07 22:26:36 UTC
Version:           1.0 devel (using KDE KDE 3.2.3KDE 1.2)
Installed from:    Mac OS X (Fink) PackagesMac OS X (Fink) Packages
Compiler:          gcc version 3.3 
OS:                Other

This is request to make the kst file attached to ELOG request
so that it is possible to come back exactly at the same
place in the data when the kst file is reloaded. 
To do so the "start" and "num" parameters of any data vector must
be set so that we can recover exactly the same data. 
This means that kst files attached to an ELOG entry should
never be in "count from end" or "read to end" mode.
Comment 1 Andrew Walker 2004-10-21 19:26:27 UTC
CVS commit by arwalker: 

When saving a .kst file from the ELOG extension save the abolsute vector position, rather than any offset positions.

CCMAIL: 90933-done@bugs.kde.org


  M +4 -4      kstdoc.cpp   1.127
  M +2 -2      kstdoc.h   1.35
  M +82 -67    kstrvector.cpp   1.64
  M +1 -1      kstrvector.h   1.26



Comment 2 Andrew Walker 2004-10-21 19:27:24 UTC
CVS commit by arwalker: 

Also for 90933.

CCMAIL: 90933@bugs.kde.org


  M +1 -1      kst.cpp   1.248


--- kdeextragear-2/kst/kst/kst.cpp  #1.247:1.248
@@ -292,5 +292,5 @@ void KstApp::customEvent(QCustomEvent *p
     QTextStream *pTextStream = (QTextStream*)pEvent->data();
     if (document()) {
-      document()->saveDocument(*pTextStream);
+      document()->saveDocument(*pTextStream, true);
     }
   } else if (pEvent->type() == KstELOGCaptureEvent) {