rgheck <[EMAIL PROTECTED]> writes: > I looked into this a bit, but came up with no answers. But here's a > guess. Maybe it's like a key-press vs key-release thing, and > itemSelectionChanged is being fired before the new row has actually > been set (ie, when the old item is deselected), whereas > currentRowChanged is fired only when the new row has been set? I guess > the answer is in the Qt sourcecode, but I've been there before and > have no desire to go back ;-)
OK, I'll just put it in. JMarc
