Component's "visibitiy" attribute

This forum contains topics that were moved from Get Satisfaction
hyounesy
Posts: 0
Joined: Tue May 24, 2011 11:34 pm

Component's "visibitiy" attribute

Post by hyounesy »

Would be useful to have a "visibility" default property for the components that can be set through editor (e.g. to have a component invisible at the beginning and turn it on through an event).

maxkatz
Posts: 0
Joined: Fri Aug 13, 2010 3:24 pm

Component's "visibitiy" attribute

Post by maxkatz »

You can get this functionality today with events. Here are the steps:

ol
liDrag and drop any component on the page/li
liSelect the screen (or just click any where in the screen), switch to Events tab/li
liAdd Load event/li
liAdd Set Property action/li
liFor Component Name, select the component which you want to hide. Note: it's name can be changed in properties/li
liFor Property Name select Visible/li
liFor Value, select False/li
liClick OK/li
liOpen the page in a web browser, the component should now be hidden/li
/ol

You can add another control to make the component above visible by adding on click event and changing the 'visible' property on the component to true.

Let me know if this works...

maxkatz
Posts: 0
Joined: Fri Aug 13, 2010 3:24 pm

Component's "visibitiy" attribute

Post by maxkatz »

hyounesy
Posts: 0
Joined: Tue May 24, 2011 11:34 pm

Component's "visibitiy" attribute

Post by hyounesy »

Thanks. That is the way I have been doing it so far. But there are some problems:
1- Custom controls, don't have a load event. So if a component is part of a a custom control, it can't be made invisible at the beginning.
2- Adding the "hide" event can some times get time consuming when there are many components that need to be invisible at start.
3- there is no visual indication in the editor on what is visible and what not.

hyounesy
Posts: 0
Joined: Tue May 24, 2011 11:34 pm

Component's "visibitiy" attribute

Post by hyounesy »

Thanks. That is the way I have been doing it so far. But there are some problems:
1- Custom controls, don't have a load event. So if a component is part of a a custom control, it can't be made invisible at the beginning.
2- Adding the "hide" event can some times get time consuming when there are many components that need to be invisible at start.
3- there is no visual indication in the editor on what is visible and what not.

maxkatz
Posts: 0
Joined: Fri Aug 13, 2010 3:24 pm

Component's "visibitiy" attribute

Post by maxkatz »

Thank you, it's good feedback. We will see what we can add in next release.

maxkatz
Posts: 0
Joined: Fri Aug 13, 2010 3:24 pm

Component's "visibitiy" attribute

Post by maxkatz »

Thank you, it's good feedback. We will see what we can add in next release.

Post Reply