> Unless I read you wrong, this is not something the "effiing bozos" > (real classy there) at Adobe loused up. > > The version of Ext that shipped in CF9 is updated from CF8. > > This means that if you performed any _native_ functions on the > objects, then there is a chance the API was dropped in the newer > version of Ext. > > This is not a CF bug. At worst, you can blame Adobe for updating > their > version of Ext, but I guess they assumed that if you were going to be > using Ext natively then you can probably handle checking the docs and > updating your code. > > A lot of people ran into this with CFGRID. They would write code to > get the grid object, ColdFusion.Grid.getGridObject, and then do stuff > with that result. > >
true; my apologies for the over the top accusation. just wanted to mention that I was not correct about the constructor returning a reference; you do have to use getWindowObject or objectCache to get the reference. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Order the Adobe Coldfusion Anthology now! http://www.amazon.com/Adobe-Coldfusion-Anthology/dp/1430272155/?tag=houseoffusion Archive: http://www.houseoffusion.com/groups/cf-talk/message.cfm/messageid:345292 Subscription: http://www.houseoffusion.com/groups/cf-talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/groups/cf-talk/unsubscribe.cfm
