PTW and I propose that we deprecate LzView.setVisible, and instead have a method LzView.setVisibility. It would support the same arguments as setVisible does now, true|false|null.
setVisibility would set the attribute LzView.visibility to its argument, while LzView.visible would (as it does now) return the actual visible state of the view (modulo datapath matching behavior dictated when visibility==null) The HTML CSS visibilty property has these legal values visible The element is visible hidden The element is invisible collapse When used in table elements, this value removes a row or column, but it does not affect the table layout. The space taken up by the row or column will be available for other content. If this value is used on other elements, it renders as "hidden" It seems like these could map pretty well to our behavior; "visible" ==> true "hidden" ==> false "collapse" ==> null and maybe we could support those as arguments, and phase out the "true/false/null" values. -- Henry Minsky Software Architect [EMAIL PROTECTED]
