> Thank you for the tqt repairs. This extends number of
> updated packages. So I try to delve deeper in patches and try to fish as well as
> all:
> 
> + Rename old tq methods that no longer need a unique name
> + Remove additional unneeded tq method conversions
> + Rename obsolete tq methods to standard names
> + Rename a few stragglers
> + ... and other tqt repairs that I have not caught
> 
> Process all of this but I will take some time. Then even
> time for testing at me and at others. I do not know if it will be before 1.
> May ready for official release. Never mind, especially that it ever will :)


Thanks. :)

Please be aware that the recent scrubbing does not mean all potentially related bugs have been resolved. As David and I discovered a few days ago, the scrubbing in tde-style-qtcurve exposed a remnant patch that likely originally was intended to overcome problems caused by the inadvertent TQ renaming. Without the inadvertent renaming, the patch caused a build failure. Yet that single event helps us now understand what to watch for with any remaining cleanup that might be needed.

With that said, I suspect almost all of the previous inadvertent TQ related bugs probably are gone. I won't be surprised if a few related bugs remain, but let's just find them and resolve them. Let's put this TQ debate behind us and move one.

Yes, the TQt transition caused some bumps and regressions and has been frustrating in certain ways. But I had a decent night's sleep, feel rested, and want to put that all behind us. :)

To anybody who hasn't, please read the wiki article about TQt. Even I understood. :)

Darrell