DBTreeTableView and Column Headers in WC

I can’t get them to paint. Am I missing something?

the headers are always shown in web client, I just did a quick test, and I do see them;
do you have a solution or example that can reproduce this issue ?

I’m on a mac, testing in firefox, chrome and safari. Even simply placing the default bean, with the default information does not show any headers. After that I try adding columns, and the data for those columns appears, but I see no headers at all. What browser do you see headers in?

firefox 3.6.12 on linux; even if you set the tree column header text, it does not show up ?

Do you mean setting the column header text using the accessor/setter on the Column object after create a new column, or do you mean setting the column header text when I add the column by passing a the header text param to the add column method?

I mean the dbtreetable.setTreeColumnHeader, that sets the tree column header text;
can you post a screenshot with your dbtreetable ?

Yes I use that method and still get no headers painted. See attached.

can you create a new solution → new form → place dbtreetable bean on it
and check it in the browser if the header is painted ? (paste a screenshot here, too)
what is the version of your Servoy ?

It paints just fine…so could it be something with my style sheet interfering? B/c I notice too that the bean in this screenshot has cell-dividing lines, which mine does not.

try to move your style sheet to the new solution, to see its influence on the bean;
then you can paste here your style sheet, so we can see what’s going wrong

try to move your style sheet to the new solution, to see its influence on the bean;
then you can paste here your style sheet, so we can see what’s going wrong

This was a good suggestion, and I had tried that as well, but that was not in fact the issue. This took me a bit to figure out, but here is the problem…

I use also the TreeView bean, which is not by default packaged with Servoy. My forms for this solution use a custom navigator form, and that form has a tree view on it. I programatically call setHeaderVisible(false) when the navigator form is shown. Apparently that call, even though it is called explicitly for the TreeView bean, and not for the DBTreeTableView bean is turning off headers for both beans!

You can replicate this easily:

1). Download and install the TreeView bean
2). Place both a tree view and a DBTreeTableView on the same form
3). Script the tree view bean as follows: elements.bean_184.setHeaderVisible(false);
4). Show the form in WC
5). Headers will be turned off for both the tree view and the dbtreetableview!

Thanks and please advise.

the issue was in the treeview bean;
you can download the latest version of the bean with the fix from
http://www.servoy.com/downloads/downloa … plugin.zip

Gabi,

Thank you very much for the fix however I have been unable to use the newest version of your treeview (which is the version I assume you patched) b/c it does not work on the Mac in SC. Can you backport this fix to the version prior to the newest one? Or post a diff/path to the plugin and I’ll apply it myself (I’m pretty sure it’s open source right?)

thanks

here is the old version with the fix : http://www.servoy.com/downloads/downloa … in_5xx.zip

Is there any info, that can be found about the differences between these two beans?

diff between 5xx and the latest treeview
features

  • allow non integer ids;
  • added onNodeSelected callback support;
  • if only the tree column is displayed, use the tree selection highlight;
    fixes:
  • row/node clicking;
  • keep tree column width setting;

oke, but Jeff, noticed/explained that this new version does not work anymore on MAC (have not tested yet, but we also have mac users)

or did I misunderstood, that this is now the default behaviour?

Jeff: do you see any difference between Mac and/or windows?

Gabi,

Thank you!

Hi Harjo,

The newest version of the treeview bean, in smart client on the Mac isn’t really functional at all in my experience. Particularly collapsing and expanding nodes that have children is very flaky, and oftentimes does not work at all.

oke, should’nt there be looked into, instead of holding & maintaining two versions?