[Kst] TR: Merging

[Brisset, Nicolas]

It seems there was a problem the first time I sent the message below (I got an answer saying that the list moderator had refused it !). Apparently, George got at least part of it but I fear it may have been truncated as there was no comment on my metadata issues :-) So here it is again (without the attachment, which I can send if there is interest), along with my
BEST WISHES FOR 2007 !

I'm sure kst, KDE and OSS in general will continue to shine even brigther. Keep up the good work, and thanks for all that you're giving as users, bug reporters, developers, and all sorts of contributors.

Nicolas

-----Message d'origine-----
De : Brisset, Nicolas 
Envoyé : vendredi 22 décembre 2006 12:51
À : 'kst at kde.org'
Objet : RE: [Kst] Merging

> I'm quite happy with the hierarchy branch now and I'd like to merge it 
> tomorrow.  If anyone has any last issues please let us know ASAP.
It seems some of the issues I have reported recently have been solved, but some remain like change data sample ranges not working, and more serious: how to update metadata when the source changes ?
There is especially one bad case, when two sources provide the same metadata (say FlightNumber) and you want to change one of them with the change data file tool. By the way, when you change sources and a label uses [FlightNumber], part of the label disappears as if the reference were no longer valid, but not updated.
I have also attached a screenshot showing that strings don't seem to get cleaned up properly. I had only one datasource loaded at the time I made the screenshot...

One thing I wanted to test is whether changing a data file while a fit was in use still leads to a deadlock, which is something I noticed recently (not in this branch) and didn't have time to report. As it stands, I'm off in a few seconds for one week of holidays, so I don't have time to do more than write this mail. I'll look into it when I'm back if nobody else has had time to do it.

To sum up, I think this branch is a nice step and quite stable, even though some issues remain. I'd say merge, and then we can finish fixing the problems. Nobody should be using this in production yet anyway, so a few days of partly-broken functionality probably won't hurt too much.

Have a Merry Christmas, and see you next year :-)

Nicolas