I desperately need a Clickthrough toggle.
If toggled on, click what is on the next layer down.
toggled off, no Clickthrough,
Currently there is no way to manipulate the z axis of widgets in Tulip or completely hide them from being rendered. The only way to do this seamlessly is to create two different steps that are almost replicas of each other.
Could you describe a bit more of the UI you are trying to build? Maybe there are some simple custom widgets you could make or you could try to achieve a similar result with enabled and disabled buttons or inputs.
An other was could be a custom widget, that contains both, the top and the bottom layer …
But I guess thats only resonable, for special cases…
Pass/click through or Layer change. This would be so that I could create a pop up instead of directing to a new step having the use have to load two steps instead of one.
Wouldn’t be a “hidden” flag more useful?
As the active status on buttons that would also just be an html attribute.
You could hide and unhide any widget, by any trigger and that would also allow layering (e.g. a modal in front of the step).
Also I think this is easy to implement, since this is the same logic as active state.
A click through would not only be more complex, but also can it lead to confusion, if you click something, but hit the thing behind…
This example is a better scenario for the feature request.
I have a custom drop down I use.
In order to see the dropdown list correctly;
- Anything other widgets that are on a higher layer than the dropdown will overlap it, covering the options (and prevent selections).
- Anything other widgets that are on a Lower layer than the dropdown will prevents interaction with anything lower than it
This is where a Click/Pass Through or Layer shifting would really help resolve this issue.
For this use case if you are able to use browser native dropdown functionality then you will not need to make the widget so tall. I cannot see what you are doing inside of the dropdown but if it is a standard dropdown then just use more standard html and the dropdown will actually work as expected with a regular sized widget.
The widget filters the list as the user input and provide an auto-complete.
The list is also longer that the tulip dropdown can use (aggregation 1000 record limit)
I’m not aware of how I could use the native dropdown (that is not the tulip widget dropdown). Could you provide more information? And would the native dropdown be able to fire triggers?