[Kst] [Bug 132954] Can't use datasource metadata in labels

Nicolas Brisset nicolas.brisset at eurocopter.com
Tue Aug 29 09:41:57 CEST 2006


------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
         
http://bugs.kde.org/show_bug.cgi?id=132954         




------- Additional Comments From nicolas.brisset eurocopter com  2006-08-29 09:41 -------
I could imagine something like [file1.dat[Provider]] for instance, but the major problem here is that file1.dat may not be a unique identifier, and using the absolute path would be *very* painful (possibly as a last resort when the filename is not enough, i.e. unique ?). Note that [file1.dat,Provider] sounds prone to problems as some files or metadata may have names with commas in them...
In the case we choose to export metadata to strings anyway, I think it would be more or less like when you duplicate all curves with the change data file tool: the new curves and vectors you get from the second datafile are all suffixed with "'", which makes them fairly easy to identify.

I think I like the "new notation" approach better, provided that I don't have to type in the full path each time. It would be nice/necessary (though maybe not easy) to ensure that labels using metadata track changes to the provider file and update automatically, like when you change a datafile at loading time (-F switch), with the "Change data file..." tool, or reload. Maybe a possibility for that would be to have a mapping defined somewhere (in a small 2-column listview dialog) between datasource instances (datasource1, datasource2, etc) and the corresponding data files (/tmp/dir1/file.dat, /tmp/dir2/file.dat, etc). One would then use [datasource1[Provider]] and check the datafile<->instance number assignment when in doubt.


More information about the Kst mailing list