Forum Discussion
Colin_McCrae
12 years agoCommunity Hero
Agreed.
I have to admit, I prefer the QTPro approach of add things as you need them.
(I also like that QTPro can load object libraries - aka name maps - on the fly at run-time. And you can easily have multiple, centralised, shared, object libraries .... hint hint!)
When it starts making this much difference to the performance of the application (I'm still convinced the AMOUNT of difference the plugins make has increased dramatically since v10.10) having them all on by default does not seem like the way to go.
But don't worry! Apart from plugin handling and name/GUI maps, I prefer pretty much everything else in TC over QTPro!
I have to admit, I prefer the QTPro approach of add things as you need them.
(I also like that QTPro can load object libraries - aka name maps - on the fly at run-time. And you can easily have multiple, centralised, shared, object libraries .... hint hint!)
When it starts making this much difference to the performance of the application (I'm still convinced the AMOUNT of difference the plugins make has increased dramatically since v10.10) having them all on by default does not seem like the way to go.
But don't worry! Apart from plugin handling and name/GUI maps, I prefer pretty much everything else in TC over QTPro!