BoundTreeView - strange child TreeNodes behaviour

0
0

I know BoundTreeView and BoundTreeNode aren’t Wisej controls. Nevertheless I need help figuring out what’s going on.

When the bound TreeView is first drawn, everything is all right. Then I have 2 issues:

  1. When I click on Refresh once, all child TreeNodes get a bigger “margin”, meaning increased left/top/bottom spacing. This happens only with child, not the root TreeNodes.
  2. When I click on Refresh a second time, all grand child TreeNodes show the Text on the left side. Root and child TreeNodes continue to show the text on the right side. I tried to draw a wider TreeView but the problem persists.

I make sure all TreeNode are disposed by:

  • using Nodes.Clear(true) on the TreeView
  • using Dispose(true) and make sure to dispose child on the TreeNode

Interesting enough, if I use Nodes.Clear() instead of Nodes.Clear(true) on TreeView, the issue 2. doesn’t show. And if I keep clicking on Refresh, sometimes the child nodes get closer again and then get a bigger margin again.

As usual I attach a WinForms / Wisej sample.

P. S. – I’m using 1.3.82 but the problem existed also on the previous release.

Attachment
WisejComplexBinding2.zip
Bugs
Share
  • You must to post comments
Filter
Sort by: Recently Active
0
0

Hi Tiago,

the issue # is WJ-8385 and it is fixed in Wisej 1.4.20.

Best regards
Frank

  • You must to post comments
0
0

Thanks for the answer Luca. As a side question, how do you track errors like this? Do you catch the JSON packet and analyse it or do you have to set breakpoints on Wisej Javascript library?

  • Luca (ITG)
    F12 in Chrome. The console should log errors in red. Wisej/qooxdoo have an extensive logging system. Then from there you can put breaks or additional log traces in Wisej.js or qx.js. They are not minified in debug mode and the full source code with comments is available.
  • Tiago (ITG)
    I suppose this means I can do it myself.
  • You must to post comments
0
0

Great catch. The size problem is caused by the png icons “pushing” out. The size in the theme is 16×16 which works fine the first time the nodes are loaded. When the nodes are updated/replaced, the code in the widget fails to enforce the icon size. Will log the bug shortly.

The other error is a client side error that I haven’t tracked down yet. It appears that the client widget is trying to display nodes without an element since they have been disposed. This is a bug too.

Thanks!

/Luca

  • You must to post comments
Showing 3 results
Your Answer

Please first to submit.