| Summary: | Scalar from scalar update problem | ||
|---|---|---|---|
| Product: | [Applications] kst | Reporter: | Nicolas Brisset <nicolas.brisset> |
| Component: | general | Assignee: | kst |
| Status: | CONFIRMED --- | ||
| Severity: | normal | CC: | netterfield |
| Priority: | NOR | ||
| Version: | 2.0.3 | ||
| Target Milestone: | 2.0.4 | ||
| Platform: | Compiled Sources | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
The scalar entry box is converting the scalar to a number at creation time - the new scalar just gets the value, so there is no updating. What is the use case for having scalars made from scalars? |
Version: 2.0.3 OS: Linux If you generate a scalar from another scalar (you can, using the Generate option even though it's a bit clumsy without the scalar selector) it does not get updated. If you create a label from it, the label obviously does not update - which is a use case we discussed recently... The name of the scalar is also not very elegant ("fixme: set _slaveName!") Reproducible: Always OS: all