P T Withington
ptw at pobox.com
Mon Nov 19 15:00:01 PST 2007
setVisibility was implemented but not advertised and setVisible was
left for compatibility (with a warning if you called setVisible with
null, as that seemed to be the case where people were getting
confused). setVisible was not deprecated though, so, I guess you
could say there was a bug in the implementation of setVisibility if it
broke something that was depending on setVisible working.
datacontrolsvisibility _is_ deprecated though, so it seems to me the
component is several revisions behind the times.
I don't follow how the setVisibility change caused the regression?
On 2007-11-19, at 17:14 EST, André Bargull wrote:
> Does someone know the current status of the "setVisibility" API-
> Change? Status of LPP-4599 ("API Change Proposal: setVisibility") is
> "open" and Fix Version is set to "Future". So it sounds like it is a
> post-RingDing issue...
> But "LzView#setVisibility(..)" is used at least in two places:
> "basegrid#init(..)" and "LzView#destroy(..)"!
> And because of calling "setVisibility('hidden')" instead of
> "setVisible(false)" in "LzView#destroy(..)", we got this regression:
> - André
More information about the Laszlo-dev