Update interaction wires across symbols / components (keep in sync)
Adding a wire to an object inside a symbol or changing a wire inside a symbol should create/change the same wire/link across other instances of that symbol in the same way styles/text etc changes other instances.
This would allow navigation to be edited throughout a project.
I love the convenience of symbols, and I love that we can now add links to objects within a symbol, but not being able to propagate that interaction to other symbols is a problem for me.
If you could create a prototype link and select to have it be applied to all layers on artboards with the same name that would greatly improve the speed for prototyping. I spent 2 hours linking up the navigation of a site that I'm testing, and having some way to mass link elements throughout the prototype would be excellent.
This should be standard - urgently needed to prevent software tedium.
Aminadav Glickshtein commented
Make it possible to save the behavior (What clicks does), in shapes. Very useful for menus.
Kathryn Guthrie commented
As it stands, XD has the capability to right-click a symbol within the Assets panel and "Highlight on Canvas".
I'd love to be able to highlight the same symbol duplicated on the canvas and wire them to the same target. For example, it would be very useful to select all hamburger icons and link to the same menu.
Just a thought!
This would be super useful. In a prototype with many artboards that are navigated by, lets say a top menu with many links, it would be useful to apply a sort of templated list of hotspots that can be applied easily to any screen that has the menu.
TL;DR: group hotspots, make them easily applicable to an artboard.
A bulk actions is required for the transitions. In my case, I accidentally had 'Ease Out' on the 'Easing' option and as I copied that art-board and created multiple edits of that art-board it kept that transition (which is the correct functionality) but now that I want to change 'Ease Out' to 'None' I need to do it one by one. Not easy, especially when there are multiple flow lines on one art-board (or lines are close to each other) the transition options don't appear when you click on the tip of the line (little arrow).
Claus Hingebjerg commented
+1 for this. When prototyping a website with 100+ pages and a fixed top navigation it would be really nic to be able to define links on a "symbol" level, eg so the logo allways goes to page 1. As i see it at the moment you have to define the "logolink" on every page.
Christoph Mauerhofer commented
I use a symbol for a navigation bar with navigation buttons that always link to the same pages (like it exists in a lot of websites, or similarly apps may have a tab-bar navigation).
It would be extremely useful to have the option to have instances of this symbol inherit these interaction links.
I agree with previous comments, that it should be an option if a symbol passes down its links to all the instances or if a symbol's links can be overwritten for each instance.
-> Some symbols are meant to be global navigation elements that always have the same content and link targets (like navigation bars)
-> Some symbols are meant to be reusable elements, that are reused with the same styling but with different contents and link targets (like buttons)
Have you tried selecting "Previous Artboard" in the dropdown menu? Or are you saying the asset would keep the attribute (like a symbol)?
Make an asset have a global transition/target in prototyping. For example, I'd love to have my back arrow asset always go to the previous screen
Exactly what I was trying to do
Jeff Swartz commented
There is a need to keep target links intact when creatiing symbols for prototype navigation.
If I make a nav bar with five menu items and turn it into a symbol so it can be persitant across mutliple boards, it would be nice if it retained the target links I put on those five nav items were saved with it. As it stands, the workaround is to create the nav symbol, click into the instance and assign links, then copy and paste that instance instead of pulling out a new symbol.
However, even there, when you paste it onto a board that is one of target links, it removes that link. That's good, but it means you have to be careful where you copy from or you're gonig to be chasing missing target link in your nav. The workaround there is to keep a separate linked up instance off-board to use as my master and cut/paste that. It should just be the symbol I'm using instead.
Benjamin Smith commented
Definitely a must. Planning links in navigation is the bane of my existence right now. I have to create empty artboards at the very beginning of the project for all my pages and link all menu items to them BEFORE I start a second page, and if anything changes in the navigation after I started copying it over, I have to manually re-edit everything.
Tomas Hejlek commented
Yes this is a MUST. I was working on a bigger project recently and it was really anoying to repeat the same action for so many artboards.
Very basic, you should hire some of invision's developers, they will teach you speed!!
Matt LaGrandeur commented
A very common scenario for us is having a common header across all pages in our site. If our header has 5 nav links, and we have, say, 30 artboards, suddenly that's 150 individual wires I have to maintain just for basic nav functionality.
I agree with @Ramses that having an option to make the links global or not would be good. But the default for links from symbols should be maintained across all instances of that symbol.
I can't believe this hasn't happened yet.
Ramsés Moreno commented
Maybe a solution would be adding a checkbox inside wire properties, like: [ ] Make this link global
David Ryer commented
• Menu or Hotspot templates (like Invision) - way too much work without
• Sticky Headers/Footers/Sidebars (like Invision) - can't prototype an important aspect
• Shrink-on-scroll Header (even Invision doesn't have this - beat them to it!)
• Type style sheets (like ID) – totally essential.
• Globally editable swatches (like ID or AI) – it's a handicap without.
• Select similar color (like AI) – would be really useful
• Global "replace font" (like ID)