Request details

Allow interaction wires/links from objects inside a symbol

I was so excited about the new symbols feature that I made all of my navbars in a design a symbol. This may be one of the most obvious uses of symbols, since every page will almost always have the same navbar. But you can't connect objects inside a symbol. Therefore, you can't connect nav items, icons, logos in a nav bar.

Either allow connects for objects inside symbols, but don't propagate them in all instances, or DO propagate them in all instances. But you HAVE to be able to connect objects inside symbols in prototype mode.

Otherwise, we can only get halfway to easily and efficiently editing UI elements like navbars, sidebars, and such.

Thanks

575 votes
Sign in
Check!
(thinking…)
Reset
or sign in with
  • facebook
  • google
    Password icon
    I agree to the terms of service
    Signed in as (Sign out)

    We’ll send you updates on this idea

    David Knell shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →

    76 comments

    Sign in
    Check!
    (thinking…)
    Reset
    or sign in with
    • facebook
    • google
      Password icon
      I agree to the terms of service
      Signed in as (Sign out)
      Submitting...
      • Anonymous commented  ·   ·  Flag as inappropriate

        So it is still not possible to update the links from a smybol when I change them in one instance of the symbol? (especially regarding nav bars). Big bummer. THX

      • Anonymous commented  ·   ·  Flag as inappropriate

        I was hoping something would be announced at Adobe Max yesterday but sadly nothing. This is really the one thing stopping our company from using XD. Not being able to wire up pages from menus really is a showstopper as far as creating prototypes goes (I know you can, but imagine having to update it in 50 different places when you want to change a menu item)

      • Anonymous commented  ·   ·  Flag as inappropriate

        Can I add my voice to the list of people saying this isn't useful in it's current form. We should only need to add links from nav bars once, then when the nav bar is dragged on to a new screen it should already be wired up.

      • Anonymous commented  ·   ·  Flag as inappropriate

        Yes, this feature is not complete. The symbol override only changes bitmaps and text, not wires. There is no way how to update wires for multiple instances of same symbol.

      • Anonymous commented  ·   ·  Flag as inappropriate

        This feature is not completed. You still can't reuse that symbol across multiple artboards and have it retain the wires you added to the elements in the symbol. You have made it only a little better with enabling to copy and paste an interaction...but what is taking so long to get the wires in a symbol to be retained in its use in multiple artboards? It is still inefficient and I cant use XD till the tool is efficient. I often have 50+ artboards....I need the symbol navigation header to retain the wires I set up when i duplicate the artboard with that navigation symbol in it.

      • Justin Ponczek commented  ·   ·  Flag as inappropriate

        Elaine, how do you use the symbol overrides feature to wire from within a symbol? Every time I try, it doesn't get propagated to the symbol instances.

      • James commented  ·   ·  Flag as inappropriate

        When converting an object to a symbol, it should not remove it's prototype link.

      • Will Viles commented  ·   ·  Flag as inappropriate

        A must-have feature. The #1 use case of symbols is for headers/footers. What do they contain? Loadsa links.

      • Brian Campbell commented  ·   ·  Flag as inappropriate

        This is a must have. Without it i have to change my global nav by hand across dozens of screens. Major PITA!

      • Thomas Hallgren commented  ·   ·  Flag as inappropriate

        Definitely would be useful. I absolutely love symbols, but if elements inside a symbol placed on an artboard was independently a link. Bliss.

      • Derek Heisler commented  ·   ·  Flag as inappropriate

        I would like a certain symbol in a menu always link to a certain art board, regardless of how many times I copy and paste that menu onto other art boards. I'd like to reduce the amount of time it would take to to relink that symbol on all art boards to the same art board. Hopefully that makes sense.

      • LESLIE ARIAS commented  ·   ·  Flag as inappropriate

        Symbols are made to repeated. The most repeated item in an application is the header and nav bar elements. So the most natural thing is to want to convert these elements into symbols.

        However, if i my nav bar into a symbol and then go on to create 50 screens. I now have to break the symbol and link each item in the nav bar for each screen. At that point the symbol feature becomes inefficient.

      • EmanueleSabetta commented  ·   ·  Flag as inappropriate

        This is the most important feature missing from AdobeXD. Without this it is impossible to design complex apps. You have to go back to InvisionApp.

      • Mike commented  ·   ·  Flag as inappropriate

        Having the option to link a standard target to a certain symbol would result in working more effectively. At the moment I have to link the same symbol on every artboard to the same target manually. Wouldn't it be great having an option where a symbol, like an arrow of which the target navigates to the previous artboard, links this target to the symbol for every artboard?

      • James commented  ·   ·  Flag as inappropriate

        I think a better and probably easier to implement, with less usability issues and overhead, will be to include linkage when copying and pasting in design mode or prototype mode. As currently you'd need to go and relink everything anyway, you might as well just duplicate the links at this stage and if users need a differing link they can easily change it. No overhead just a massive win. Upvote here: https://adobexd.uservoice.com/forums/353007-adobe-xd-feature-requests/suggestions/13041930-copy-paste-should-preserve-interaction-wires-links Tom also said this wouldn;t be too difficult to implement too.

      ← Previous 1 3 4

      Feedback and Knowledge Base