[kst] [Bug 372265] "Change Data File" does not update file name references in text box

[C Barth Netterfield]

OK.

as of the next commit, I (will) have fixed data strings and data scalars so 
that they are saved properly, and so that -F and the change data source both 
work for them as expected.

Now we have to decide what to do with the datasource automatic primitives:

I think there are three options:
1) they are permanently associated with the  datasource.  eg:
	[tmp.dat (DS1):FRAMES (X1)]
is the number of frames for the file tmp.dat - now and forever.  -F doesn't 
change this.  Change datasource doesn't change this.  Saving and reloading 
doesn't change this.  The primitives can not be edited in any way.
With the exception of some minor bugs, this is the logic of how they have been 
implemented.

2) When a datasource is first used, all of the primitives associated with the 
datasource are automatically created as normal datascalars or datavectors.  
They now show up as normal primitives in all of the dialogs, and can be 
optionally edited and changed just like any other dataprimitive, including in 
the change datasource dialog, or -F.  However, since they are just 
automatically created normal data primitives, "purge" would delete them 
(unless we add some sort of flag to them).

We would have to decide which strings and scalars from a datasource should be 
created automatically, and which ones should be left to manual creation.
This requires some (tractable) new code.

3) automatic strings and scalars are removed alltogether.  If you want them, 
you create them, just like any other datascalar or datastring.

(In any case we should add create string/scalar icons to text entry dialogs.)

thoughts?

cbn
On Wednesday, November 30, 2016 9:15:07 PM EST Nicolas Brisset wrote:
> https://bugs.kde.org/show_bug.cgi?id=372265
> 
> Nicolas Brisset <nicolas.brisset at airbus.com> changed:
> 
>            What    |Removed                     |Added
> ----------------------------------------------------------------------------
> CC|                            |nicolas.brisset at airbus.com
> 
> --- Comment #3 from Nicolas Brisset <nicolas.brisset at airbus.com> ---
> Hi all,
> 
> I believe automatic scalars are useful and I would not like having to create
> them manually. For instance, they can be used to display some stats in text
> form along with a graphical plot. For me they should be preserved, and of
> course recomputed and labels using them (if any) refreshed automatically
> when the data is reloaded from the same file - or from another file.
> 
> The same should essentially happen with strings from datasources in my
> opinion.
> 
> Where it gets more tricky is when you have more than one datasource. In that
> case we have to keep track of which datasource provides which object to be
> able to update the right one(s) in case one of the datasources change.