Can't fit box width

[perrybrus]

I have a 320px wide artboard. I have a box that goes across this. This box is also 320px wide. So why can't I make it match the width of the arboard? As you can see from the leftmost grab the box goes outside the dark gray border that is my 320 artboard, the left grab shows the opposite side where it's too short. So why don't you just drag the handles in or adjust it manually you may ask? Cause when I do that it skips the border and snaps to a point that exceeds the 320 width of the arboard! I can't nudge it one pixel and I can't adjust the handles, it always goes outside the width of the artboard. It never match the width. And Yes, the box measures 320px in width. And no, there's no border on it.

What is going on in cases like this?! It's like a forced snapping routine is on but there's no such thing in XD. I also experience this in other cases where it's impossible to freely move things cause it always snaps outside the other element I'm trying to match.

[Preran]

I tried reproducing your issue but wasn't able to.

- I created an artboard that was 320 px wide

- Created a rectangle of the same width

- Moved it around and it snapped to the artboard.

[perrybrus]

It doesn't help me that you were able to preform this task without issues I'm afraid. I'm stuck with this and more related issues. As mentioned before, XD is an unstable program. What works for one person fails for another. There are so many factors that come to play it seems. I have colleagues with the same issues and colleagues that don't have the same issues. Some occur randomly, other repeatedly etc.

I tried this same task on other artboards but I'm still stuck with the same issue. Whatever I expand or shorten won't move freely as it snaps outside other borders and exceeds or becomes shorter than the other elements. Same thing with single vector elements, they are acting like I'm dragging something close a negative magnet pole and it chooses to position either longer or shorter in comparison to what I'm next to. Never at the exact same. Also, when I have one single vector element on the canvas and introduce another one, dragging one of them freely and with no increment won't happen. It always "snaps" and settles down on all other places than right next to the other. When trying to enter x and y coordinates I'm amble to place them next to each other, but that doesn't apply to dragging handles on boxes.

I just asked a colleague on W10 to try to preform the resize task on my exact file, he wasn't able to and he experiences the exact same error. He then created his own replica of this and failed to widen the box as well. Just like me the box snaps to a point that either exceeds the width of the artboard or gets too short. When handlebars are dragged they refuse to stop at exact measurements but moves in increments. Always snapping to whatever is NOT the correct position. I would call this a major bug.

If there's any Adobe engineers out there that works with  XD, does your application really support Windows or should we expect a plethora of bugs at this stage still? Does Xd support the use of 4K machines attached to a monitor with a native 2560x1440 resolution with the OS upscale at 200%? Is it something you want to tell us? Anything that could lead us closer to understanding how you think in developing XD? Cause there are so many errors, instabilities and buggy experiences that I don't experience in other Adobe programs. XD is by far the product that struggles the most, meaning it creates a plethora of errors and instabilities on movement, type treatment, file handling, tool errors etc etc etc.

I did the following experiment: I made a vector box and added zero color (100% transparency is XD's equivalent of no color added) to a border set to 0, that box added a border of 1px. Why? I then emptied the stroke width field by deleting the zero and hit shift to activate the change, that made the number 1 appear again automatically AND it started to change and add values to the background blur feature! Now this is getting interesting, right? Are we still talking stable program with no bugs? I changed the type size value by entering the type size value box and changed the numbers, that changed the opacity slider instead. Over and over again. I could go on, it's been like this all the time. Nothing changes after update, only new bugs are introduced it seems. This leads me to raise the legitimate question: Is XD really compatible with W10?

[Randy Edmunds]

Thanks for reporting bugs! I've heard a couple other reports that sound similar to this, but they are intermittent so we are still trying to nail down the cause.

Does this happen all the time? For me, it sometimes happens immediately after switching to a different doc, but stops happening after 5-10 seconds.

Please let us know if you can isolate a set of steps that causes it to happen reliably.

Thanks for your help,

Randy

[perrybrus]

Most of the errors described here are chronic, meaning it happens all the time. Type size alterations creating a change in the opacity slider is a golden classic that's been with W10 users ever since first beta release. I remember reading something about that being in fixed back in late 2015 so I hoped it was a housefly but it obviously never was as it is very much still around. When it comes to sizing of boxes to match another vector element and movement this is also something that occurs all the time, having said that it was less apparent in prior versions, seems to have become worse since last two updates. Again, I'm talking W10 here. There's alot of buggy stuff going on in the properties panel as described and these are constant errors. I wished Adobe could take a long hard look at that and fix the issues once and for all, not to expect that a program is perfect, but at least these basic functions used repeatedly should deliver a consistent result when used. Find a proper and expected manner in which to change property values. Should be enough to copy what works in more robust apps such as PS or IN. Can't really see the advantage of doing things different in XD. If you click inside the type size field and change the numbers this should be ample, instead of double clicking and/or single clicking and selecting all numbers and not clicking shift to apply afterwards cause that will affect the sections underneath in the UI.Etc etc.

[Ares Hovhannesyan]

IMHO XD needs match object to artboard function.

[Randy Edmunds]

Thanks for the additional info.

Regarding Opacity, it works like this: if focus is on canvas, then typing any number sets opactiy of selected elements to that level. For example, typing 8 sets opacity to 80%, and typing 25 (fast) sets opacity to 25%.

The Property Inspector (PI) works like this: if you change a field and hit Enter, the value is committed and focus is returned to the canvas (so you can continue working faster). If you hit Tab, the value is committed and focus remains in PI and is moved to next field.

There are some cases where focus does not follow these rules and we are trying to fix all of these cases. It would be most helpful to us if you can provide step by step instructions to help us identify cases where focus changes unexpectedly so that we can fix them.

Thanks,

Randy

[perrybrus]

I'm not referring to what happens when you actively use the the opacity slider, I'm referring what affects the opacity values and that is as mentioned alot of things that is peripheral to that property. Like using the type function for instance, it is a major bug that changing type properties affects the opacity slider. It's like turning the light switch on and instead the water starts running. And this has been going on for years now. When I hit Tab the focus isn't next field, it actually avoids activating any alterations in the properties panel I'm at and instead it alters NEXT section. Make changes to the border properties and hit Shift, then it MAY apply changes but not always, but what always will happen is that the next section in the properties panel will receive an alteration. Blur, shadow, opacity, whatever comes after what I'm trying to change. If I single click inside the type size section nothing happens, no cursor blinking or anything, if  however double click inside the type size section then I'm able to change the size number(s) - but hitting enter doesn't apply anything here. Never done. The expected pattern is: Click ONCE inside the type size section, add the values, hit Enter or/and Tab to apply. If you press Tab that could take you to next step/section in the properties panel without adding any changes to that particular field that is next in the UI. But that's not what happens in Xd.

[Randy Edmunds · Accepted solution]

I put focus in opacity field, changed value, and hit Tab and the focus goes to the next field. What type of element do you have selected? The PI is a little different for some elements. I tried with a Rectangle, Ellipse, and Path.

I truly believe you when you say that weird things are happening to you, but we need to be able to isolate each individual problem and also be able to reproduce them here to be able to fix them. Maybe it's 1 bug or maybe there are a more than 1. The descriptions you've given so far are too general to understand exactly what's happening and I'm not following some of the terms (e.g. "type size").

Please start a new post for each problem. Please provide an exact set of steps on how anyone can reproduce 1 single problem. It's easiest if your recipe starts with something like:

1. Create new document

2. Add N Artboard(s)

3. Add these shapes...

If it can't be reproduced with a new doc, then hopefully you can send in a small sample doc that has the problem.

After that, recipe should say:

4. Select this element(s)

5. Click in [whatever] field in PI

6. Type [whatever text] and hit [whatever keyboard key]

Describe every mouse click, mouse move, and keyboard click.

Results: what happened

Expected: what did you expect to happen

Can you create a video or GIF of what you're doing? Those can be helpful sometimes.

Be sure to specify that you're on Windows 10 and the version.

Specify if you are using a mouse, trackpad, touch screen, or whatever.

Thank you,

Randy

[perrybrus]

Randy, it's not like I'm presenting unique and new issues here. All of them have been raised both here and in the bug report site, perhaps except from the rectangle sizing problems. With type tool alone there should be enough for the whole year and I haven't even touched on the issues where the textbox height gets cut in halve and all I see when typing is fragments of type and 90% white. I have presented them yet again here. I can't spend more time on them making videos etc. I respect that your not able to recreate the issues, but that should lead Adobe to conclude on compatibility issues and instability problems. It's a classic sign of that. Now I need to work, meaning switching to Axure for the moment.