WARN:GridBody:isc_ListGrid_1_body:setTabIndex()

[stonebranch2]

I am seeing a number of setTabIndex() warnings. I've included one below for reference.

SmartClient Version: v9.1p_2014-06-27/Pro Deployment (built 2014-06-27)

FF ESR 24.6.0

[ERROR] [opswise] - 11:50:46.077:XRP3[E]:WARN:GridBody:isc_ListGrid_1_body:setTabIndex(): Passed index of 4694. This method does not support setting a tab index greater than 999.  Setting tab index for this widget to 999
    Canvas.setTabIndex(_1=>4694)
    ListGrid.updateMemberTabIndex(_1=>[GridBody ID:isc_ListGrid_1_body])
    Layout.$2w()
    Layout.drawChildren()
    Canvas.draw(_1=>undef, undef, undef, undef, undef, undef, undef, undef, undef, undef)
    [a]MathFunction.invokeSuper(_1=>[Class ListGrid], _2=>"draw", _3=>undef, _4=>undef, _5=>undef, _6=>undef, _7=>undef, _8=>undef, _9=>undef, _10=>undef, _11=>undef, _12=>undef, _13=>undef)
    ListGrid.draw(_1=>undef, _2=>undef, _3=>undef, _4=>undef)
    Layout.layoutChildren(_1=>"member changed visibility:[ListGrid ID:..."[55], _2=>undef, _3=>undef)
    Layout.reflowNow(_1=>"member changed visibility:[ListGrid ID:..."[55], _2=>4)
    anonymous()
    [c]EventHandler.runTeas()
    [c]EventHandler.$h2()
    [c]Comm.$h0(_1=>[object XMLHttpRequest], _2=>"isc.Comm.performXmlTransactionReply(21, ..."[55], _3=>undef)
    anonymous([object Event])
        "if(_11.readyState!=4)return;isc.Comm.$h0(_11,_10)"

Regards

[Isomorphic]

This would typically occur if you have code which explicitly calls "setTabIndex" to a value higher than the TAB_INDEX_FLOOR. The SmartGWT system automatically assigns tab indices for components by default, starting at the tab index floor and increasing from there.
If you as a developer want, you can take components out of this auto-assigned tab order by explicitly setting the tabIndex attribute, but it is expected that you will stay below the TAB_INDEX_FLOOR - otherwise you'd start to collide with auto-assigned tab-indices.

If you're seeing these warnings in a case where you're not explicitly specifying tab index, there may be something else going on here (we have made some small changes in this area recently). In this case, please do test with the latest nightly build just to make sure you havent hit a temporary regression, and assuming the issue persists, please show us a test case and we will attempt to reproduce.

Regards
Isomorphic Software

[stonebranch2]

We don't have code that explicitly calls "setTabIndex", so the next time we pick up a daily build, we will keep an eye out and post back here with an example to reproduce if the warning still exists.
Thanks