[acarur01]

I still have the problem I am experiencing in the video. When my problem starts to happen, I see a bunch of stacktraces. I don't know if you took a look at the email I sent but I have ones below. Should I be concerned with these? They are marked as "info" so I'm assuming not but I am running out of ideas here...

09:44:27.004:XRP8:INFO:resize:page$content$$content1$tree_body_vscroll_thumb:resize of drawn component: new width/height: 16,557, old width/height: 16,558, delta width/height: 0,-1
    Class.getStackTrace(_1=>undef,  _2=>undef,  _3=>undef,  _4=>undef)
    Canvas.resizeBy(_1=>0,  _2=>-1,  _3=>undef,  _4=>undef, undef, undef, undef, undef)
    Class.invokeSuper(_1=>[Class StatefulCanvas],  _2=>"resizeBy",  _3=>0,  _4=>-1,  _5=>undef,  _6=>undef,  _7=>undef,  _8=>undef,  _9=>undef,  _10=>undef)
    StatefulCanvas.resizeBy(_1=>0,  _2=>-1,  _3=>undef,  _4=>undef,  _5=>undef,  _6=>undef)
    Canvas.resizeTo(_1=>16,  _2=>557,  _3=>undef,  _4=>undef)
    Scrollbar.setThumb()
    Scrollbar.setVisibility(_1=>"inherit",  _2=>undef,  _3=>undef,  _4=>undef)
    Canvas.show()
    Canvas.$u2()
    Canvas.$ux(_1=>"redraw")
    Canvas.$ut(_1=>"redraw")
    Canvas.adjustOverflow(_1=>"redraw",  _2=>null,  _3=>true, undef, undef, undef, undef, undef)
    ** recursed on Class.invokeSuper

9:44:27.437:TMR7:INFO:resize:page$content$$content1$tree_body_vscroll_thumb:resize of drawn component: new width/height: 16,422, old width/height: 16,557, delta width/height: 0,-135
    Class.getStackTrace(_1=>undef,  _2=>undef,  _3=>undef,  _4=>undef)
    Canvas.resizeBy(_1=>0,  _2=>-135,  _3=>undef,  _4=>undef, undef, undef, undef, undef)
    Class.invokeSuper(_1=>[Class StatefulCanvas],  _2=>"resizeBy",  _3=>0,  _4=>-135,  _5=>undef,  _6=>undef,  _7=>undef,  _8=>undef,  _9=>undef,  _10=>undef)
    StatefulCanvas.resizeBy(_1=>0,  _2=>-135,  _3=>undef,  _4=>undef,  _5=>undef,  _6=>undef)
    Canvas.resizeTo(_1=>16,  _2=>422,  _3=>undef,  _4=>undef)
    Scrollbar.setThumb()
    Scrollbar.setVisibility(_1=>"inherit",  _2=>undef,  _3=>undef,  _4=>undef)
    Canvas.show()
    Canvas.$u2()
    Canvas.$ux(_1=>"row animation complete")
    Canvas.$ut(_1=>"row animation complete")
    Canvas.adjustOverflow(_1=>"row animation complete",  _2=>undef,  _3=>undef, undef, undef, undef, undef, undef)
    ** recursed on Class.invokeSuper

[acarur01]

For another scenario I cannot reproduce as a standalone, I see this error when I expand the node in IE

10:06:37.815:TMR8:WARN:Animation:Attempt to fire registered animation:{ID: "_0",
target: [TreeGridBody ID:page$content$$content1$tree_body],
callback: Obj,
duration: 300,
elapsed: 68,
totalFrames: 8,
currentFrame: 1,
maxDuration: 900,
acceleration: undef}
Caused an error:Invalid argument.

[Isomorphic]

Stack traces like that "resize of drawn component" trace are happening because you enabled a bunch of diagnostics and this is the output from those diagnostics. These do not indicate errors unless you see them with the diagnostics off.

As far as an offsets issue, generally, you can create this if you are leaving fixedRecordHeights as true, but not setting enforceVClipping, and yet putting content in the rows which causes them to be taller than the cellHeight you set. If setting fixedRecordHeights:false corrects the issue, this is the problem, although the better fix might be to figure out how you've added content that causes the rows to expand.

[acarur01]

Setting fixedRecordHeights to false fixes the issue in Firefox but not in IE..I still get the following error:


09:39:03.206:TMR0:WARN:Animation:Attempt to fire registered animation:{ID: "_0",
target: [TreeGridBody ID:page$content$$content1$tree_body],
callback: Obj,
duration: 300,
elapsed: 68,
totalFrames: 8,
currentFrame: 1,
maxDuration: 900,
acceleration: undef}
Caused an error:Invalid argument.
09:39:08.650:XRP8:WARN:Log:Error:
'Invalid argument.'
in http://localhost:8080/cwf/isomorphic/system/modules/ISC_Grids.js?v=55173
at line 684
GridRenderer.setRowHeight(_1=>2, _2=>NaN, _3=>null, _4=>"", _5=>true, _6=>true, true)
GridRenderer.$28n(_1=>1)
GridRenderer.finishAnimateRowHeight()
GridRenderer.finishRowAnimation()
ListGrid.dataChanged(_1=>undef, _2=>undef, _3=>undef, _4=>undef, _5=>undef)
Class.invokeSuper(_1=>null, _2=>"dataChanged", _3=>undef, _4=>undef, _5=>undef, _6=>undef, _7=>undef, _8=>undef, _9=>undef, _10=>undef)
Class.Super(_1=>"dataChanged", _2=>Obj{length:0}, _3=>undef)
TreeGrid.dataChanged()
dataChangedObservation()
Tree.remove(_1=>Obj{ID:itemTree/Items}, _2=>undef)
Tree.$27e(_1=>Obj{ID:itemTree/Items}, _2=>Obj{ID:$root$}, _3=>undef)
Tree.$640(_1=>Obj{ID:itemTree/Items}, _2=>"id", _3=>"parentId", _4=>undef, _5=>"$root$")
Tree.linkNodes(_1=>Array[2], _2=>undef, _3=>undef, _4=>undef, _5=>undef, _6=>undef, _7=>undef)
[c]Class.fireCallback(_1=>$376(), _2=>"dsResponse,data,dsRequest", _3=>Array[3], _4=>[DataSource ID:page$content$$content1$tree$ds], _5=>undef) on [Class DataSource]
Class.fireCallback(_1=>$376(), _2=>"dsResponse,data,dsRequest", _3=>Array[3], _4=>undef)
DataSource.fireResponseCallbacks(_1=>Obj, _2=>Obj, _3=>Obj, _4=>Obj)
DataSource.$38b(_1=>Array[2], _2=>Obj, _3=>Obj, _4=>Obj, _5=>Obj)
DataSource.$50h(_1=>Obj, _2=>Array[2], _3=>Obj)
** recursed on [c]Class.fireCallback

[Isomorphic]

See previous response re:enforceVClipping and whether you've got content forcing the row height larger.

The actual error here suggests that you've somehow make the pixel height of rows impossible to calculate. We're not sure how this would be possible, but it might involve CSS styling you've applied to all cells/rows, so try removing all styling that's not coming from SmartClient as a means of troubleshooting this.

[acarur01]

I will continue to investigate what is wrong but for now I have disabled animateFolders and I no longer have issues

[chimpeenuts]

I realize this thread changed topics slightly, but I'm having the exact same issue as the original post.

I've created a very simple test case that re-produces the Collision WARN message I am seeing.

First,

Version: SC_SNAPSHOT-2012-02-22_v8.2p/EVAL Deployment (expires 2012.04.22_05.30.04)

Browser: Firefox, 10.0.2

I have a brand new Smart GWT Eclipse project with a simple TreeGrid that is fed by a SQL-based Datasource. When I attempt to re-fetch data for the TreeGrid, I get the following WARN message:

[ERROR] [testtree] - 16:34:54.824:MUP9:WARN:Log:ClassFactory.addGlobalID: ID:'isc_Tree_0' for object '[ResultTree ID:isc_Tree_0 (created by: isc_TreeGrid_0)]' collides with ID of existing object '[ResultTree ID:isc_Tree_0 (created by: isc_TreeGrid_0)]'. The global reference to this object will be replaced

Here is my ENTIRE (single) source/code file:

public class TestTree implements EntryPoint {

	VLayout _mainLayout;
	TreeGrid _tree;
	Tree _treeProperties;
	Button _button;

	public void onModuleLoad() {
		SC.showConsole();
		
		_mainLayout = new VLayout();
		_mainLayout.setWidth100();
		_mainLayout.setHeight100();
		
		_button = new Button("Click ME");
		_button.setHeight(40);
		_button.setWidth(80);
		_button.addClickHandler(new ClickHandler() {
      public void onClick(ClickEvent event) {
	      _tree.fetchData();
      }
		});

		_treeProperties = new Tree();
		_treeProperties.setNameProperty("name");
		_treeProperties.setIdField("id");
		_treeProperties.setParentIdField("parentId");
		_treeProperties.setIsFolderProperty("isFolder");
		_treeProperties.setOpenProperty("isOpen");
		_treeProperties.setTitleProperty("title");
		_treeProperties.setReportCollisions(false);

		_tree = new TreeGrid();
		_tree.setWidth100();
		_tree.setHeight("*");
		_tree.setDataProperties(_treeProperties);
		_tree.setDataSource(DataSource.get("categoryDevice"));
		_tree.setAutoFetchData(true);

		_mainLayout.addMember(_button);
		_mainLayout.addMember(_tree);

		_mainLayout.draw();
	}
}

When the UI/webpage loads, and I click the 'Click Me' button I get the above WARN message in the Development console.

According to the original few posts, the original poster was able to solve this by NOT returning the parentNode in the DSResponse. But since I am using the built-in SQL-based datasource, I don't create or even see the DSResponse.

I don't think there's a much simpler example. This is very easily reproducible and seems like a bug. While the WARN message doesn't hamper the application's functioning it is the only WARN message being thrown and it would be nice to prevent it.

Has anyone else gotten this issue with a SQL-based datasource?

[Isomorphic]

This warning should be safe to ignore and have now user-visible impact.
We've made a change that will make it go away in the 3.1d branch

Regards
Isomorphic Software