This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 94697

Summary:	Need visual effect for components that support rendered attribute
Product:	obsolete	Reporter:	bugbridge <bugbridge>
Component:	visualweb	Assignee:	Pegah Sarram <pegah>
Status:	STARTED ---
Severity:	blocker	CC:	pegah
Priority:	P3
Version:	5.x
Hardware:	PC
OS:	Windows ME/2000
Issue Type:	ENHANCEMENT	Exception Reporter:

Description bugbridge 2007-02-06 18:52:22 UTC

Original status: 5-Cause Known; Suggested Status: NEW

Original Target Release: mako_dev; Suggested Target Milestone : Dev


Description:
This was produced on update 7.

This bug is been posted from the following forum thread.
http://swforum.sun.com/jive/thread.jspa?messageID=203094

When I bind property ???rendered??? of a component to a bean???s property , the
component disappears from visual page designer. This makes us hard to see where
the component located on the page and very difficult to layout other components
relative to the one with property ???rendered??? set.

I suggest that these components should be visible at designing stage so we can
lay out other components easily..



xxx@xxxx 2005-04-21 11:49:49 GMT

Evaluation:
This is because when the VB expression is evaluated, Insync creates a new
instance of Boolean and returns the value. The default value is false, and so
rendered gets set to false, which makes component become unrendered in the designer.

Comment 1 Pegah Sarram 2007-07-17 01:05:58 UTC

This issue needs to be fixed in insync by setting the default value of the Boolean to true.

Comment 2 _ sandipchitale 2007-07-17 03:31:05 UTC

Insync cannot set the default value of the Boolean property to true by itself. This should be handled by component's 
designtime renderer by showing a ghost component (maybe) when the rendered attribute's value evaluates to false (at 
design time).

Comment 3 Pegah Sarram 2007-07-17 21:14:33 UTC

After speaking with Sandip and looking at the issue in more detail, here is my evaluation.
 
The rendered attribute means that the component should not be shown. In fact, setting that attribute via binding works
as expected. The issue is that when the rendered attribute is set to false via the checkbox, the component doesn't
disappear right away. This probably mislead the user to think that the incorrect behavior is with the property binding. 

The bug is in the designer where it doesn't update the component after its property is changed. If you refresh the page,
or close and open the project, the component disappears. I'll file a new issue against the designer for that.

However, to address the user's concern, we could render something like a dotted box around the components that have
their rendered attribute set to false (or bound to a property). We need to come up with some kind of a visual effect for
all the components that support the "rendered" attribute across the board. I will downgrade this issue to P3 and mark it
as enhancement.