Hi !
I like Indigo really but I can't figure how I can achieve this :
The widget is on a screen between 2 other containers. So when I clicked on the button, the widget is a state 2 and expand BUT over the container below.
What I want is that the container below is pushed down as the widget box expands.
Any help is welcome ! Thanks !
Normal State
https://dl.dropboxusercontent.com/u/20902263/IMG_20150831_140035.jpg
State 2 (Actual)
https://dl.dropboxusercontent.com/u/20902263/IMG_20150831_140042.jpg
State 2 (Ideal)
https://dl.dropboxusercontent.com/u/20902263/IMG_20150831_140123.jpg
Hi Benjamin!
To achieve what you want I see two different options.
You can either use a repeater control or redefine the button interaction in the screen.
For the first option, to use a repeater control you will have to add two items (one for the screenpart and another one for the container) and make the first item autoheight. By doing that when the screenpart grows the item that contains it will also grow, and it will push the container down.
For the second option, you can redefine the click interaction for the button in the screen. The second state for the screen will move the container and it will also change the widget/screenpart to make it looked expanded. The disadvantage of this solution is that you will have to repeat the changes of the screenpart in the screen.
We are considering adding an option to trigger an interaction after a screenpart instance has reached a particular state. I guess that funcionality would be useful for this particular scenario. what do you think?
Please let us know if we can help you in any other way.Regards,HelenaIndigo Studio Team
Ok I'll give a try !
Trigger interactions would be very useful as some of your competitor (like UXPin) have already this function (with some possible actions like 'Resize', 'Move', etc) and it's useful to acheive some interactions
Thanks
Hi, Benjamin.
The one thing which makes Indigo Studio prototyping different and faster is direct manipulation. As in, instead of using a dialog to pick a UI element from a document outline, you visually select and modify the UI element of interest. This approach aids in two ways:
That said, we would like to to continue this approach. What Helena mentioned was allowing users to view the state of the screenpart or widget when used in a screen, and manipulate it in a similar fashion as shown above. Say you have a screenpart with two states (A & B). One idea is to surface the interactions defined on the screenpart state A, and using it to trigger a new screen state. This will create a new screen state, and also set your screenpart instance to State B.
I am not saying this is available right now. Simply sharing an approach we are considering.
I think it would be a great improvement to animation to have such possibility to say 'If button#1 is clicked then move container#2 to y:254'
I'm trying the repeater but as this screenpart is on every screen that means I have to deal with repeaters on every screen ?