Like you, we typically wait a while before upgrading. One reason is exactly this sort of thing - lack of backwards compatibility causing significant recoding across a large number of applications. We can't afford to stay on the cutting edge when doing so means a couple weeks of work every time we upgrade.
I haven't even looked at QV11 yet, so I can't help with the mentioned OnSelect trigger for an object. Maybe it doesn't even exist - the only OnSelect I know about is for fields. Maybe the quote is referring to what happens when you select a value in a list box. You would simultaneously fire the OnSelect and OnActivate actions. And maybe these actually execute in parallel, causing unpredictable results. And maybe I'm missing something, but if that's the case, the obvious solution seems to be always executing one before the other, such as always firing the OnActivate before the OnSelect. Now the results are predictable. Easy. Fixed. Maybe it only seems easy to fix because I'm ignorant of the real issues, though.
And don't we still have this problem with the OnSelect and OnAnySelect triggers? Won't these "collide and results will be unpredictable"? Better remove those triggers too, then, right? *sigh* I really don't know what QlikTech is thinking.
As you say, hopefully they'll put the triggers back in. I just don't understand what makes these triggers so broken, so impossible to fix, that they decided it was better to force thousands of their customers to recode their applications.
