Hi.
Thanks for the reply.
Regarding the visibility and opacity, the request is to have this
controllable as an action (on mouse click, roll over, etc.) and not as an
ordinary property. Like we used to have in Hyperscript and later in Lingo
(“set the visibility of member X to 0, set the visibility of member Y to
1”)
Yes, I know it can be achieved by Javascript, however not all users (myself
included) are proficient enough in javascript and the beauty of Hype is in
the ability to achieve so much without writing code.
Thanks all the same.
Moshe
Agreed. No argument. Ultimately its a question of priorities.
Nevertheless, my past experience with the multimedia production world
(since 1988) showed that controlling the visibility of objects
interactively was one of the most common functions.
Anyway, we love hype, with or without this function.
A compromise would probably be to add this to the current setElementProperty() method’s list of property names. That way you could use the API to control this. Therefore, not bloating the UI but giving the non-proficient Javascript users the ability to code it with relative ease in a function.
Although it means creating multiple timelines or being creative with the timeline if you wanted this to happen to more than one element at different times hiding/being visible or to create a toggle-like instance for one. It’s quite complicated to set up and understand for a first timer. By creating a function and using the setter method I would think it would be better suited. Just my opinion