So I’m a fan of moving in that direction. I’m not saying that’s wrong but it might be why the experience is especially jarring.ītw, here are a couple old ideas riffing on inline interactions. For example, there are 2 “Set is selected of…”, 2 “Set”, and multiple “Hide/Show” actions that could’ve been combined. it was always pretty hard to distinguish multiple attributes within an action.Īlthough one thing I noticed with the OP’s workflow is that he creates a separate action for each attribute instead of combining them together. The actions and attributes are clearly denoted vs having everything displayed in a single, continuous line of text. Also, I like the breathing space afforded here. This solution allows you to quickly switch between objects and modify their interactions. Perhaps the old way of doing things wasn’t technically broken, but the workflow was definitely cumbersome. Perhaps there are changes they can make to allow this to be more efficient, like the comment about having a simple vs advanced view. I think this is a welcome iteration in their design. In RP9, you can manage them fully within the list without the dialog box. They’re already listed in RP8 and you can take limited actions on them, but to fully manage them you have to open them up in a dialog box. The idea here seems to be about allowing interactions to be managed inline. Build in the old menu again and make it accessible to power users again.Īs it is currently implemented in Beta 9, I’ll probably just go crazy if I want to manage the interactions in our previous projects. But PLEASE, it allows power users to continue to use the previous input. For my sake, keep the input (which I still don’t think is any better). I know you’ve put a lot of work into creating the reworked interaction input. I just can’t believe you want to advertise the new version of the interaction as optimized UX. in the new version you just can see 3-4 steps before you have to scroll. As you can see in the pictures of the thread creator, the old version had a pretty extensive overview of the whole macro. If you’re not familiar with it, you’ll be guided step-by-step through the creation process.īut for everyone else, the new way of inputting and managing interactions is a real nightmare: the input is slow and absolutely confusing in any view. The revised version of Interaction Input may be suitable for newcomers who have never worked with interactions before. Well AxureBoutique, a technology writer and teacher, focuses on Axure prototype design and product design.The headline of this thread describes it quite aptly: " What have you done? If you like the article, please share it with others with page link, thanks for your supporting! ❤ If you have any questions and suggestions, please leave a message. Note: Click here to download the completed RP file for this tutorial (RP 10 or up). The disadvantage is that there will be screen jamsĪs shown in the above image, after the dynamic panel changes to the last state, wait for 1000ms, and the current page will refresh again, thus realizing the loop. That is, at the last action, reload the current page. As shown in the above image, when the dynamic panel is loaded, a series of actions are executed, and the last action triggers the initial series of actions to realize the loop.ġ. Generally, an interaction of the widget triggers a or a set of interaction(s), and the last interaction will trigger the initial interaction.Ģ. 1.By the interaction settings of the same widget, the loop can be realized.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |