The whole application is acting unstable. Frequent crashes, menues not working, layer panel not working etc etc. This is the norm with XD. Re-innstalling the application sometimes works, but the issues occurs so often that re-innstalling the program each time gets ridicilous. When reading the forum I observe that I'm not alone experiencing all these problems, on the contrary it's very common. Do wish Adobe would test the product instead of using us as crashtest dummies.  ... View more

I've spend alot of time on this issue and it seems to me that artboard links won't work with components and also some times on copied artboards. I have one artboard where the top menu is the master component, the links added to that menu to all the other artboards wont work. No link hand when mouse over of text. No nothing. Yet the text is linked and the link arms are all showing in prototype mode. XD also fails when an artboard is copied and renamed and then put between two artboards, then if you add a link from that artboard on the whole artboard (not a singel element) it often fails to work. Its not included in the row of artboard and it "skips" to the next. These are just a few of the quirky instabilities of artboard links. There are more and they keep coming for each so called upgrade. ... View more

Some things in XD only works in theory cause if I have many elements grouped then reaching the lowest stacked element is not possible with a single Ctr+click for selection. I find myself forced to double click repeatadly in order to select that object or element. If I have two or three objects stacked in a group then a single Ctrl+click normally works - but not always then either. It's this XD instability that annoys me.   Thanks for the tip on path convertion and how that works. I'll make sure I think of that next time I select rectangles.   ... View more

Hi, thanks for sharing. I'm not referring to Files but as mentioned the content in Published. Commonly shared files for development, like code specs and prototypes. It's not possible to organize those in folders on either CC desktop application or CC web interface. ... View more

It's july 2020 and I also have this same problem. The component and asset system is not working as intended at all. And it ruins any copy document as well. It's a nightmare. ... View more

"Your prototype at 100% is bigger than your browser window." But it's not bigger than my browser window. The resolution at my end is 2560x1440 and the viewport in CC is considerably clipped in height. When I increase the zoom level in the CC viewer (not in browser) the content is shown a little bit bigger inside the clipped viewport but its not bigger than my resolution or browser viewport. Why does Adobe clip the viewport at the bottom anyways? No need for that.  I also account for task bars and browser interface when setting the viewport size, I even include the 15px wide scrollbare face, but I don't think thats relevant here as the viewport within the CC frame is cut. It's like looking at something inside an inline frame with a set overflow. I don't understand why things are displayed that way in CC, cause thats not an autentic preview. Example: If I made this thing in Dreamweaver and did a preview it wouldn't present my design inside a clipped or restricted frame like it does on the cloud presentation, it would just show me what I made in a 1:1 relation. ... View more

No. As mentioned it doesn't change anything to copy artboards in prototype mode and paste it onto a new document in prototype mode. No matter what mode I'm in the links are still lost. Please inform the deveopment team in XD about this bug, its getting very old. ... View more

No change on latest update that I received in CC today. Not sure what you mean by switching to default zoom? As mentioned default zoom is 85.4% and as mentioned that's the only time anything works. But on all other zoom levels sticky elements  comes apart as mentioned. Is it not supposed to work on any other zoom? One would think 100% should be the default zoom. ... View more

Do wish you can make sure every feature works in local prototype mode on both Windows and Mac before release anything. If not every so called "upgrade" will feel like a downgrade. Mouse gestures is a must. Most designers in my company don't use a laptop or trackpad when designing. We use a stationary workstation with a seperate keyboard and mouse. And most users navigate with a mouse on desktop applications, at least in my country. ... View more

As mentioned Im trying to copy artboards from a document to another document. When I do that the links between artboard are all lost in the copy. In other words I only get the artboards but not the links. It doesn't change anything to copy in prototype mode or design mode, it's the same outcome. This has been an angoing problem with XD, I remember reporting on this years ago as well. The problems seem to return again and again, specially after the so called upgrades.  ... View more

After last XD update the software crashes all the time for no appearant reason. I've had countless crashes and they also occur when the software isn't being used but minimised.   W10 Pro. Version 1909. OS Build 18363.900 XD 30.1.12.4       ... View more

Yes your right. It's more like inconsistent behavior than unstable behavior. I experience that alot with XD. ... View more

Yes, export for web has always been default for this project. There's no content in Variables.       ... View more

You could say it makes sense both ways, but I agree that it would be annoying to receive all the assets if your not interested in anything but the artboard itself when copying from one document to another. However, I actually DO receive the character styles and the component when Ctr+C / Ctr+V artboards from one open XD document to another open XD document. The weird thing here is that I don't get the colors with me all the time, but sometimes I do. And when I share the copied document for development (Share for development) the colors are right there in the specs! But they are not in the document itself. So to me this looks like a bug or at least instable behaviour? ... View more

The section in Code specs is called Variables. As mentioned in my post it says ""When designers add colors and character styles to the assets panel in XD, they will appear here as design variables for you to use." Well, I have done that but as mentioned they are not available in the Variables section. ... View more

Yes, same outcome on all files. I've made a new file as you requested and it happens there as well. Same default 85.4% zoom level and if increased then the sticky top menu section looses fixed position and scrolls out of the picture when scrolling back up.   https://xd.adobe.com/view/00f24add-a5e0-4591-8f54-a0c8fd874058-55a1/   XD 30.1.12.4 Winver 19.09 OS build 18363.900   ... View more

I know but due to corporate rules I'm not at liberty to share iteration files, so I'm constantly seperating selected elements and creating new documents with stripped elements in order to remove identity and share stuff, and in that process the whole consept is lost cause its very time consuming to re-arrange and simulate a similar setting etc. ... View more

Thanks for following up and for sharing that code specs demo. Obviously I need to use the eye icon in the layers palette to hide state content from states instead of the opacity slider, actually all official demo videos I have seen on states are using the opacity slider. However I'm having problems with using the states, it is something completly wrong here. When I select a state it goes back to default when I try to edit it and after that all the states are gone and the component tekst in the component section is grayed out. This started after last update, it must be a bug.    ... View more

Yes, I hear you. Same procedure. I don't think hidden states should be included incode specs.   I wanna add that in addition the whole states feature in XD is buggy. I'm lucky if I'm able to actually select a single state without the whole UI switching back to design mode and graying out the Componant text. Most times I'm only able to get one chanse to prepare each state with content before it all shuts down, selecting them again after that is bingo. I've shared that in another post and I see that more people share that same problem on W10. ... View more

Hm, that's right. It's defined as a path. I doubled clicked a new box and saw that it was converted to a path, that introduces a second issue cause the only way for me to actually select a box that is grouped with a bunch of other elements is either ungroup a bunch of nested groups one by one, or double click the box in order to select it. If doing that converts that element to a path then it makes selecting very tidious. The example you saw was just the box container seperated from a nested layout with heaps of stuff going on inside that container. Can't ctr+click either like some tutorials claim as that doesn't select the single layer but always something surrounding it as well. Makes it even worse if that whole container and its content is a component.   PS. I shared a new doc with a new box that wasn't a path to code specs and corner radius was spesified in the specs as expected. ... View more

I'm unable to achive any functional states if I only use the eye icon in the layers palette to hide states, therefor I'm forced to do it the only way available by using the opacity slider. The latter action is including all the layers in the state interaction in the code specs. As you know there's no inteactive features in code specs as it only shows the markup of each element, so including the invisable layers from the states creates confusion for someone who can't see anything but static layout. ... View more