Bug 128748 - use of scalar in definition of static vectors
Summary: use of scalar in definition of static vectors
Status: RESOLVED WORKSFORME
Alias: None
Product: kst
Classification: Applications
Component: general (show other bugs)
Version: 1.10.0
Platform: unspecified Other
: NOR wishlist
Target Milestone: ---
Assignee: kst
URL:
Keywords: investigated, triaged
Depends on:
Blocks:
 
Reported: 2006-06-07 14:57 UTC by Marc-Antoine Miville-Deschenes
Modified: 2018-10-21 04:41 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Marc-Antoine Miville-Deschenes 2006-06-07 14:57:56 UTC 
Version:           1.2.0_devel (using KDE 3.1.4)
Compiler:          gcc version 3.3 20030304 (Apple Computer, Inc. build 1495)
OS:                Darwin (Power Macintosh) release 7.9.0

It would be very useful to be able to use scalars
in the definition of static vectors (N, min and max).
Comment 1 Andrew Walker 2006-06-07 20:15:10 UTC 
If the scalar value subsequently changes I'm assuming that you wouldn't expect the vector values to change to reflect this.
Comment 2 Netterfield 2006-06-17 04:09:26 UTC 
MAMD, can you give an example of how this would be used?
Comment 3 George Staikos 2006-06-17 16:11:44 UTC 
  This really is straightforward.  It's just another reimplementation of 
KstVector.
Comment 4 Andrew Walker 2007-12-13 19:58:42 UTC 
Additional information would be useful:

What would you like to specify with scalars (min, max, number of points, etc.)?
Do you want to be able to use expressions as well as scalars?
Would you expect the vector values to be dynamic?
Would you expect the vector length to be dynamic?
Comment 5 Andrew Walker 2009-04-14 20:33:57 UTC 
Will address once the expected behaviour is well defined, which is not currently the case.
Comment 6 Peter Kümmel 2010-08-14 14:20:02 UTC 
Could be still open in Kst 1.
Comment 7 Andrew Crouthamel 2018-09-20 22:04:24 UTC 
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days, the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please set the bug status as REPORTED so that the KDE team knows that the bug is ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 8 Andrew Crouthamel 2018-10-21 04:41:12 UTC 
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!