Bug 106307 - Scalars from Vectors not referenced by a Curve are not updated
Summary: Scalars from Vectors not referenced by a Curve are not updated
Status: RESOLVED FIXED
Alias: None
Product: kst
Classification: Applications
Component: general (show other bugs)
Version: 1.1.0
Platform: unspecified Linux
: HI normal
Target Milestone: ---
Assignee: George Staikos
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-05-25 23:40 UTC by D. V. Wiebe
Modified: 2006-05-29 18:13 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description D. V. Wiebe 2005-05-25 23:40:03 UTC
Version:           1.1.0 (using KDE 3.4.0, compiled sources)
Compiler:          gcc version 3.3.5
OS:                Linux (i686) release 2.6.11

Scalars derived from vectors which don't happen to be part of a curve aren't initialised or updated.  If you use a scalar (RMS, Mean, Max, Last, &c.) derived from such a vector on a label, plot, or what have you, the value is always zero.

If you later create a curve with the vector, the scalar starts updating.

Steps to reproduce:

1. Create a new vector using the new vector dialog box.  Do not place it in a curve.

2. Display scalar.  The value will be identically zero.
Comment 1 George Staikos 2005-05-26 04:58:53 UTC
  This is somewhat by design right now, but is a consequence of the update 
reworking.  The vector was never updated because it was never used.  It could 
be setup to push an event onto the update thread to update that vector, but 
keeping it in sync is a conceptual issue that I need to think about for a 
bit.

   We could actually have a clean solution for this by the end of the year if 
the development goes as planned and we implement some extended data object 
tools.  (more on this later when we're closer to implementing it)
Comment 2 George Staikos 2005-07-06 16:14:54 UTC
Since we are moving to the new label mechanism, it will be postponed until that is integrated.  It will have an update() mechanism which should fix this.
Comment 3 George Staikos 2005-08-08 21:50:06 UTC
I'll try to clean this up before I leave.
Comment 4 Andrew Walker 2005-08-12 20:37:18 UTC
I think the same issue applies for the viewing of scalar and vector values in the various View dialogs.
Comment 5 Netterfield 2006-02-15 01:49:08 UTC
Required for 1.3

A detailed plan should be reviewed before this is attacked.
Comment 6 George Staikos 2006-02-24 16:08:59 UTC
SVN commit 513171 by staikos:

A bunch of label work mostly derived out of planck requirements but generally
quite useful.

1) Invalidate labels when the reference scalars/vectors/strings/expressions
change.  This makes realtime top-level labels work, assuming the data they're
pulling from is updated.  That part will be fixed separately and this patch
will be reduced as a result.
CCBUG: 106307
2) Don't play around with \n and \t.  Our new editor supports them properly so
we can handle both real CR and Tab, and \n and \t.  Fixes munging of labeltext
BUG: 122386
3) Add preliminary support for \textit{}, \textbf{}, \underline{} to the parser
and renderer, and a stub for \textcolor{}{} to the parser.  In general the first
three work, but cannot be nested.  The last one does not work yet since there is
no color parser.  Testcases to follow once nesting is handled.


 M  +110 -1    libkstapp/kstviewlabel.cpp  
 M  +12 -1     libkstapp/kstviewlabel.h  
 M  +43 -6     libkstapp/labelrenderer.cpp  
 M  +6 -0      libkstapp/labelrenderer.h  
 M  +60 -12    libkstmath/labelparser.cpp  
 M  +3 -0      libkstmath/labelparser.h  
Comment 7 George Staikos 2006-05-29 18:13:35 UTC
Done