Okay, so I’m trying to understand here. By looking up documentation, I see that you can place images in your file and link them to an image on your file system, so not embedding them in the file. (I’m assuming you’re not talking about inserting links to images on the Internet via URLs.) When the document opens, it loads up the image and places it in. In some apps, updating the file on the file system will update the image automatically without any intervention, and in other apps, changing it on the file system won’t update until you either manually refresh or relaunch the app.
This scenario is what I was defining as “dynamic linking.” Smart Objects (as I’m defining them in my head) are elements that are in a CC file format (like Photoshop or Illustrator). Am I misunderstanding your request for external links?
I tried again and again, after restarting, after the last XD update. Still here.
I tried in Photoshop layers, no problem.
I noticed if I select more than 5 characters, it does not occur (see gif for example)
thank you for the feedback.
I tried on a new document, and it still does this bug. I tried to restart XD, same issue. It seems to come from the double "--". See the file attached
edit: Nope, still bug without the "--"
Windows10 version 1809
We use a server with GIT for version control and team work. Can't use cloud, therefore can't link Styles and Colors to another document...
It works with components, why this choice for colors and styles ??
Hi, thanks for the feedback
I think you misunderstood my point, I just wanted an instance of a button to be slightly different from the master but still rely on the master for some parameters.
Anyway, after trying to make a capture to explain the process, I found out that it works finally fine. I think the bug occur because I worked with assets created using the old component system form a file created prior the may update. See the difference with a component created with freshly added instances against the old one. I used the same technique for both component... strange
If you wanted to know if the nested component is an instance or a master, then the answer is it's an instance. In that case, reseting the nested component while adding an instance is plain dumb. I do want some parameters to be dependent of my master button (such as color or round angles) but I don't want the modified parameters to be reseted (such as text of the nested button). Which is the behaviour that happen when I copy an instance on the artboard or when I do the trick detailled before.
I'm not sure to understand your answer... You want to know if I'm editing the master component rather than an instance of it?
If that's what you meant, then yes, I'm editing the master component on my artboard (see xd file in the first post) and the expected behaviour would be that when I add a new instance, the nested component shouldn't be reseted.
As I said in my second comment (see xd file attached too) If I duplicate the nested component, then delete the first one to replace it by the copy, it works fine.
Do you need a more detailled video of the actions involved ?
More info on this bug : I noticed that if I duplicate the nested component on the artboard, then the bug does not occur. See gif and xd file attached
same shit ! lost 1 hour of work !!
290 votes14 comments · Adobe XD: Feature Requests » 02 : Prototype mode · Flag idea as inappropriate… · Admin →
73 votesfeature-in-the-backlog · 15 comments · Adobe XD: Feature Requests » 03 : Sharing on the web · Flag idea as inappropriate… · Admin →
218 votes44 comments · Adobe XD: Feature Requests » 03 : Sharing on the web · Flag idea as inappropriate… · Admin →
429 votesfeature-under-review · 26 comments · Adobe XD: Feature Requests » 03 : Sharing on the web · Flag idea as inappropriate… · Admin →
24 votes9 comments · Adobe XD: Feature Requests » 03 : Sharing on the web · Flag idea as inappropriate… · Admin →
There was some negative feedback received when we removed the navigation arrows from prototypes, so, this change was reverted and other solutions are being considered.
1,111 votesfeature-started · 25 comments · Adobe XD: Feature Requests » 02 : Prototype mode · Flag idea as inappropriate… · Admin →
165 votes48 comments · Adobe XD: Feature Requests » 03 : Sharing on the web · Flag idea as inappropriate… · Admin →
Sorry for the confusion. This behavior in XD is intentional. Only the user who created a prototype link is able to update that link. The thinking is that the owner for the link may not want others making changes.
At the moment, the only way for multiple people to update a prototype at the same URL is to be logged in with the same Creative Cloud account. We are however discussing adding the ability to specify more than one owner for a prototype – and we could then allow all owners to update the prototype link. It sounds like this is what you were expecting and the behavior you would like to see, is that correct?
As a studio of 5 users working sometimes on the same files, this is a nightmare...
They should stay visible on the table but greyed. And this way, masked artboard won't get exported in the prototype preview
127 votesfeature-under-review · 13 comments · Adobe XD: Feature Requests » 01 : Design mode · Flag idea as inappropriate… · Admin →
While XD doesn’t yet have this feature to save gradients in the color picker popup’s swatches, you do have several other options today:
- Store gradients in the Assets panel swatches: open the Assets panel on the left side (View > Assets), and click the “+” next to Colors. Then select any other object and click the gradient swatch to apply it to that object.
- Copy gradient fills between objects: use regular Copy on the source object, then select the destination object and choose Paste Appearance.