278536 - Tree documentation: setCellText and redrawing.

Status: RESOLVED WONTFIX

(Developer Documentation Graveyard :: Mozilla Platform, defect, P5)

Description

[Michael (GoodWill)]

This is relations to bug 278484.
Thee is little documentation for the tree object out there, but I learned this
bit and with bz's blessing I am filing a bug an bit about setCellText and redrawing.

------
Unlike many other controls the data for the tree.view is stored in a custom data
type that the developer defines. The developer needs to write a
contructor/prototype for the view of any tree and apply to that view.
The function with teh constructor are responsible for manipulating and
maintaining the data. Basically they are get, set and functions of the tree.view

As of today the best place to figure out how the tree works is look at the
pageinfo.js and pageinfo.xul of Seamonkey release 1.8a6 (look at the attachments).

As I learned from the esteemed bz the developer is responsible for setting up a
way to have tree redrawn when the underlying data has been changed. 
That can be done by issuing of the invalidate functions after the change has
occured.
There are many invalidate methods available: invalidate(), invalidateCell(row,
column),and etc..
http://www.xulplanet.com/references/objref/TreeBoxObject.html#method_invalidate

The attachment above show several implementations and gives you a general idea
on how to use them.

Comment 1

[Michael (GoodWill)]

Attachment: Tree refresh samples

Draft 0.1. Sample xul and JS file to demostrate how to uset setCellText and
invalidate methods of the tree.view

Comment 2

[John Karahalis [:openjck]]

Automatically closing all bugs that have not been updated in a while. Please reopen if this is still important to you and has not yet been corrected.

Comment 3

[John Karahalis [:openjck]]

Reopening for review by Sheppy.

Comment 4

[David Bruant]

This seems like a XUL feature, so Mozilla-internal documentation.
What's the good component/product for that?

Comment 5

[BMO Automation]

MDN Web Docs' bug reporting has now moved to GitHub. From now on, please file content bugs at https://github.com/mdn/sprints/issues/ and platform bugs at https://github.com/mdn/kuma/issues/.