inactiveEditor context for a cell without having cleared the previous one

[DSingh]

Using SmartClient Version: v8.3p_2013-02-08/PowerEdition Deployment (built 2013-02-08)

Can you give some input on below error?

[ERROR] [gwt] - 09:34:28.537:MUP1:WARN:inactiveEditorHTML:isc_ESItemsWidget_1_1:creating new inactiveEditor context for a cell without having cleared the previous one.
[a]MathFunction.getStackTrace(_1=>undef, _2=>undef, _3=>undef, _4=>undef, _5=>undef)
ListGrid.getInactiveEditorCellValue(_1=>Obj, _2=>18, _3=>6)
ListGrid.getCellValue(_1=>Obj, _2=>18, _3=>6, _4=>[GridBody ID:isc_ESItemsWidget_1_1_body])
[o]GridBody.getCellValue(record=>Obj, rowNum=>18, colNum=>6, gridBody=>[GridBody ID:isc_ESItemsWidget_1_1_body])
GridRenderer.$22k(_1=>Obj, _2=>18, _3=>6)
GridRenderer.refreshCellValue(_1=>18, _2=>6)
GridBody.refreshCellValue(_1=>18, _2=>6)
GridRenderer.refreshCell(_1=>18, _2=>6)
GridRenderer.refreshRow(_1=>18)
GridRenderer.placeEmbeddedComponent(_1=>[HLayout ID:isc_HLayout_23])
GridRenderer.$29d()
GridRenderer.modifyContent()
Canvas.$ra()
Canvas.redraw(_1=>"Showing editor", undef, undef, undef, undef, undef, undef, undef)
[a]MathFunction.invokeSuper(_1=>[Class GridRenderer], _2=>"redraw", _3=>"Showing editor", _4=>undef, _5=>undef, _6=>undef, _7=>undef, _8=>undef, _9=>undef, _10=>undef)
GridRenderer.redraw(_1=>"Showing editor", _2=>undef, _3=>undef, _4=>undef, undef, undef, undef, undef)
** recursed on [a]MathFunction.invokeSuper

Thanks,
Deepak Singh

[Isomorphic]

In some cases we write out inactive FormItem HTML -- HTML that looks exactly the same as the item would within a dynamicForm, but has a different DOM ID and various other different attributes to avoid confusing the event handling, and other systems within the SmartClient framework.

The most obvious case where we do that is within ListGrids with "alwaysShowEditors" set to true.

The warning you are seeing indicates that the framework believes that it may have written out this kind of inactive HTML for some cell within a ListGrid more than once (potentially leading to duplicated DOM IDs or other confusion).
If you're not seeing any actual bad behavior within the application, this warning may potentially be being reported over-zealously and be safe to ignore, but to be on the safe side, if you can show us a test case where we can reproduce the problem we will take a look (and either fix the underlying issue, or clean up the error if it is in fact unnecessary in the case you're seeing it).

Thanks
Isomorphic Software