I want to be able to define conditions/rules based on, for example, user input that could conditionally change the state of my screens and/or control the flow for the user. This would imply remembering what users have put in and being able to reference it in the rules.172 votes
We added support for triggering interactions based on changes to the text input. Check it out in the latest version of Indigo Studio. You should see an in-app update mid next week.
Check the following blog post to see a summary of what’s new: http://goo.gl/ymMWNT
We added actions to rotate or mirror icons in the latest version of Indigo Studio.
Check the following blog post on what’s new in Indigo Studio 2015 Vol.2
Would like to be able to jumpstart the development process from the prototype by getting HTML5 type code from it that we can then plug into the app being developed.90 votes
We have started working on this—basic extraction of these code assets. If you would like to review/provide feedback on this, please let us know.
I design applications for the Hebrew language, and we need support for RTL text and input.21 votes
The scenario I'm looking for is for example:
I have a wizard made in a screenpart, that I use on different states from one screen. I would like to display different states of the screenpart on different instances.7 votes
Something like this..6 votes
We agree that would be handy!
Currently we remember the font choice for the project, and screen size when creating a new screen in the project. Give this model a chance, and let us know how it’s working out for you.
Instead of a global settings, we are exploring the route of remembering recent values. That in a way may overlap with your request. What say?
Indigo Studio Team.
As discussed in this post: http://www.infragistics.com/community/forums/t/108903.aspx
I would like to have a participant of a usability study to follow his own path in a prototype, next to your closed task studies you have now. Because it doesn't matter in what order, or what part of a toggle-group-element is being clicked. Following a predefined path, like you offer now, could guide the participant too much, and could possibly frustrate the user and quit the study. Whereas a free-flow study I could analyse if the user 'gets' the function of the page, for example.2 votes
Good news is that we have started work on this. We are also researching offering open-ended task as an option.
Have a bunch of annotations/callouts and would like to hide them when I'm editing the prototype.1 vote
We already have done this on our internal build (for V2).