<html><head><style type='text/css'>p { margin: 0; }</style></head><body><div style='font-family: Arial; font-size: 10pt; color: #000000'>... and my last mail for today!<br>----- "Barth Netterfield" <netterfield@astro.utoronto.ca> a écrit :
<br><br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">>
I believe there are many issues there:<br>>
1) the .kst not being used correctly when reloading the file ("Reimund's bug") <br> </blockquote><div>> I haven't looked at this. I presume this is related to storing configuration options in the kst file?<br>That's what I suppose, but I've lost track of the last changes. I just tested again, and now it seems to work. But as I'm a bit confused, maybe the best would be if Reimund could test it again with the latest svn version. Reimund, is this possible?<br></div>
<div> </div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
2) the -F switch not being implemented in kst 2.x yet (not really a bug, rather a missing feature). While we're at it, we may want to look at implementing more than one -F switch (-F1, -F2, etc), as explained in <a href="http://bugs.kde.org/show_bug.cgi?id=115662" target="_blank">http://bugs.kde.org/show_bug.cgi?id=115662</a><br> </blockquote><div>> I have committed the</div><div>> kst2 [-F <filename>] [-f <startframe>] [-n numframes] [-s <skip>] [-A] <kstfile></div><div>> file override usage. I have not added the idea of -F1 -F2, etc.</div>
<div><br>> NOTE: the -F option opens a new datasource which may be of a completely different type, and so ignores any datasource configuration parameters that may have been stored in the kst file.<br>Oops! I had not thought of that, but I believe it's an issue! In *all* the cases I used -F, the files had the same format. I'm pretty sure chances are much higher that you get the data correctly if you reuse the settings and only change the filename, than reading the file as if it were completely new. If we want to refine it a bit, we could possibly distinguish: <br>- same file type (i.e. datasource plugin) => reuse settings stored in the .kst<br>- different file type: read as if it were new<br></div>Your current approach would have forced me to tune the default settings to that format so that the data can be read :-( I don't know how hard it would be to do and how convinced you are, but I'm very confident that it's much safer "my way"...<br>
<div><br>Nicolas<br></div></div></div></body></html>