Error closing one of my tabs -- have spent hours to no avail.

[bschrameck]

SmartGWT version: v8.2p_2012-09-07/LGPL Development Only (built 2012-09-07)
Running IE9 dev mode, GWT 2.4.0

For some reason I have a single trouble tab in my application that I can't close. I've narrowed it down to a single picklist that is causing the problem, however this picklist is used on many other tabs without an issue.

When I close the tab, I get the following error:

17:45:06.782:MDN0:WARN:Log:Error:
	'Function expected'
	in http://localhost:8080/myapp/sc/modules/ISC_Forms.js
	at line 1333
    crashed in:  FormItem.invalidateDisplayValueCache()
    Use a pre-9.0 Internet Explorer for best diagnostics, otherwise Firefox or Chrome

When I remove the offending picklist it closes just fine. The panel contains a SearchForm and a ListGrid. For what it's worth, I also get the following warning upon creation of the tab:

17:44:51.711:MUP8:WARN:Log:method ignore on [SelectItem ID:undefined name:operatorName] overridden with non-function: 'true'
17:44:52.145:MUP8:WARN:Log:method ignore on [TextItem ID:undefined name:rsaNum] overridden with non-function: 'true'
17:44:52.154:MUP8:WARN:Log:method ignore on [TextItem ID:undefined name:orderId] overridden with non-function: 'true'
17:44:52.801:MUP8[E]:WARN:Log:method ignore on [ImgButton ID:undefined] overridden with non-function: 'true'
17:44:52.814:MUP8[E]:WARN:Log:method ignore on [ImgButton ID:undefined] overridden with non-function: 'true'
17:44:52.835:MUP8[E]:WARN:Log:method ignore on [ImgButton ID:undefined] overridden with non-function: 'true'
17:44:52.855:MUP8[E]:WARN:Log:method ignore on [ImgButton ID:undefined] overridden with non-function: 'true'
17:44:52.866:MUP8[E]:WARN:Log:method ignore on [ImgButton ID:undefined] overridden with non-function: 'true'
17:44:52.893:MUP8[E]:WARN:Log:method ignore on [ImgButton ID:undefined] overridden with non-function: 'true'
17:44:52.906:MUP8[E]:WARN:Log:method ignore on [ImgButton ID:undefined] overridden with non-function: 'true'
17:44:52.933:MUP8[E]:WARN:Log:method ignore on [ImgButton ID:undefined] overridden with non-function: 'true'

I thought this might point to an ignored data source field, but I can't for the life of me find anything. Are there some other reasons this warning might be thrown? Why are all of the IDs undefined?

Any direction would be appreciated.

[bschrameck]

I'm still having errors with this. It seems that the SmartGWT JavaScript invalidateDisplayValueCache code calls the following (I've formatted the code for readability):

if (_2 != null && this.isObserving(_2, "dataChanged")) {
    this.ignore(_2, "dataChanged");
}

But it's crashing on the call to this.ignore with the error I posted earlier (function expected). I think it has something to do with how the drop down detects changes to the DataSource, however I don't know enough about the framework to say.

Please advise, thanks,
Brian

P.S. - I'm having this error with more than one tab, it seems. All of them have something to do with a drop down that is assigned an optionDataSource I think.

[bschrameck]

Digging a little further, it seems that the combo boxes that are having issues have the wrong value for their ignore attribute.

Here's what a combo box that works looks like:

function isc_Class_ignore(_1,_2){var _3;var _4=isc.$a9[_2];if(_4!==_3&&_1[_4])this.ignore(_1,_4);var _5=isc.$ah+_2;if(!_1[_5]||!_1.$ba)return false;var _6=_1.$ba[_2],_7=_6.$dh;for(var i=0,_9=_6.length;i<_9;i++){if(_6[i].target==this){if(_7)
_6[i].$di=true;

Here's what one that does not work looks like:

true

[bschrameck]

I think I may have found the problem.

I have a DataSource for another screen that inherits from the DataSource for this screen. On that other screen I ignore some of the fields. Apparently ignoring the fields on the other screen's DataSource *also* ignores the fields for the first screen.

Is this by design or is it a bug? It doesn't seem like this should happen. Any fields I ignore (or alter in any other way) in the inherited DataSource should not affect the fields in the DataSource I am inheriting from.

Thank you,
Brian

[Isomorphic]

We can't tell because we can run the code, and not being able to see the actual code everything is just speculation. If you can isolate the problem to a minimal, runnable test case we can take a look.