It'd be nice to be able to save interactions inside widget. For example we create a widget «Main menu» for website. We can use this widget on every page and then we can easy change the set and the order of items of menu across prototype. But it's only visually. Today we have to manually setup "Goto screen"-interaction for every menu item on every prototype page.
dear antetype team, this feature would be very handy. we are creating a 200 page wireframe with different menus. copying the menus by hand .. oh lord .. hoping the client will not change the site structure. unfortunately i discovered this after we decided to use antetype. of course the program is great(!) but i was a bit shocked finding out about this.. :)
thanks for your reply. in our case it would be best if widgets would simply allow sharing interactions except if non-updated. A option shared/individual for an Action within an Interaction would be one step further. kind regards
must say, this is becoming really a serious issue for me because i cant use the privilege of synchronized widgets at all. when i'm updating my nav-header-widget all the interactions of objects in it (e.g. menulinks) are gone... (?) wether they are widgets themselves or not. so this means everytime anything changes in the nav-header-widget i need to manually copy and replace it on every page. mh to be honest, i chose to use antetype because of its functionality to synchronize objects. manually copying is exactly the thing i wanted to avoid.. :)
while looking at the problem we discovered one bug, which might be your problem. In the following structure, each screen has the same menu with goto-screen-actions to jump to the various screens:
Moving for example "Screen A" to a different position inside the menu and updating the menu widget removes the goto-screen-action from the "Screen a"-cell on all screens.
We have a fix for this one which preserves the actions. Do you have other scenarios where the actions are lost after update?
We have code freeze for the upcoming 1.6.2-release, so this will not make it into this release. Just wanted to make sure we don't miss other problems.
I know this does not remove the need for shared interactions. Thanks again for bringing up the issue.
Felix, thanks for good news.
Additional scenarios – on your example.
Problem 0 is not about interaction for widget. And it’s not serious, but it’s problem anyway.
0. Duplicate screen ‘c’ and rename current (selected) screen to ‘d’.
Select menu item ’Screen c’ – Surprise. Now the menu item leads to the 'Screen d'. When I rename the screen I thought that new rename the newly created screen (copy). I expected that when I create a copy of it immediately becomes selected and once I can work with it. Perhaps the current behavior makes sense. But due to the fact that the original and the copy and named the same I do not understand that you have selected the original and I change the old screen and all references to it.
1. Duplicate menu item ‘Screen c’, rename it to ‘Screen d’, and update whole menu widget.
Result - OK. All screens have 4 items in the menu.
Now I want add interaction to new (‘Screen d’) menu item and update whole menu widget.
Add interaction – OK.
Update Menu widget – Problem. No green button and no green dot for ‘menu sample’.
2. A similar problem when I want to change the interaction.
Add new screen ’screen a - alternative version’ – OK.
Select menu item ‘Screen a’ and change Action->Screen = ’screen a - alternative version’. – Problem. No green button and no green dot for ‘menu sample’.