| Summary: | vector generation does not update all properties | ||
|---|---|---|---|
| Product: | [Applications] kst | Reporter: | Nicolas Brisset <nicolas.brisset> |
| Component: | general | Assignee: | kst |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | ||
| Priority: | NOR | ||
| Version: | 1.x | ||
| Target Milestone: | --- | ||
| Platform: | unspecified | ||
| OS: | Solaris | ||
| Latest Commit: | Version Fixed In: | ||
The vector will currently only be updated if it is part of a curve. We could force the update by doing the following in KstSVector: internalUpdate(KstObject::UPDATE); in KstSVector::changeRange(double x0, double x1, int n). Any good reason not to do this? On Wednesday 16 November 2005 16:35, Andrew Walker wrote: > ------- We could force the update by doing the following in KstSVector: > > internalUpdate(KstObject::UPDATE); > > in KstSVector::changeRange(double x0, double x1, int n). Any > good reason not to do this? Looks right to me. That's exactly what internalUpdate was created for (and why it's protected). Call internalUpdate to update the static vector properties. |
Version: 1.2.0_devel (using KDE 3.4.0, compiled sources) Compiler: gcc version 3.4.3 OS: SunOS (sun4u) release 5.8 To reproduce: - start kst - datamanager -> new vector -> generate - settings: from -10.0 to 10.0, 1000 points - OK: in the datamanager, properties say from 0 to 0 while viewing the vector values show that it has been generated correctly - edit the vector from the datamanager: the from/to values are set to 0 The values entered should obviously be reflected in the datamanager UI ("properties" column) and taken into account when editing the vector.