Jump to content
You must now use your email address to sign in [click for more info] ×

dantaylr

Members
  • Posts

    100
  • Joined

  • Last visited

Posts posted by dantaylr

  1. Is this still the best method?

    I believe manually typing in a width or height while transform each is turned on should automatically make all the objects the same width or height based on what was typed. The current behavior doesn't seem nearly as useful.

    To circumvent this I am dragging my images into Figma, which does do this. When multiple objects are selected it lists the width, height, and positions as "mixed". Manually typing a value forces all of the selected objects to scale to that value. I would love to see this in AD in the future.

  2. 41 minutes ago, Dan C said:

    Many thanks for providing those for me and my apologies for the delayed response here!

    I can confirm that I've been able to replicate both issues using an iPad Air, both with and without a Folio case - it appears to be due to specific angles detected by the accelerometer in the iPad, the keyboard will reopen or the adjustment dialog will close, causing the issues shown in your screen recordings.

    I'm logging these both with our developers now, as the accelerometer shouldn't be determining either of these functions, as far as I'm aware.

    I hope this helps :)

    Wonderful. I'm so excited to hear this will be addressed. Thank you!

  3. Okay I was just able to replicate this on a 12.9in iPad Pro M2. It wasn't as easy but I was able to get the issue to start happening if I slightly lifted the base of the iPad that was touching the counter so that the angle changed slightly. So basically if you hide the keyboard, and then change the angle slightly the keyboard pops up again. Perhaps the accelerometer in my 11in causes this to trigger more easily.

  4. 1 hour ago, Dan C said:

    Many thanks for verifying that for me! I assume when you mention 'low angle mode' you are referring to the following setup?

    s-l1600.jpg

    I'm not able to replicate this currently - can you please provide a screen recording showing both issues for me? Including the aforementioned keyboard issue in the recording may also help me to understand your workflow.

    If you're unsure how to take a screen recording, please check out our FAQ linked below - 

    Many thanks once again :D


    Here are two screen recordings.
     

    The first demonstrates the keyboard failing to go away while in the position you sent the picture of. 
     

    The second is taken in Affinity photo and demonstrates some adjustment layer bugginess when the iPad is in this position. You'll notice the adjustment layer's edit controls disappear frequently and it has to be tapped again. In addition when I move the curves controls the image responds correctly for a second but then fails to respond at all. This all works just fine once the iPad is propped up at a steeper angle. At 37 seconds in the second video I prop the iPad up further and you'll notice the curves layer responds just fine. 
     

     

  5. This is a bug since V1. When using the official folio case for the 11in iPad Pro in the low angle mode the keyboard will refuse to hide. It will hide and then immediately come back. I'm wondering if this an Apple issue or an Affinity issue but it doesn't appear to do this in any other app so I'm tempted to say there's something in designer that's the culprit. 

  6. I'm not sure if this is a bug or if there's something I'm missing here. If I create a symbol and copy it, both symbols are linked so I can make changes to them. The symbol also shows up in the symbols panel. If I then copy both of the symbols to a new document, they remain linked to eachother but they don't show up in the symbols panel for the new document. Is there any menu that describes or allows you to control the linkage between these two objects?

  7. FYI crash still happens on the public beta. And it isn't when exporting it's when you exit the export menu. If you go to export and then hit cancel it crashes. I'm losing lots of work due to this because auto save isn't kicking in frequently enough. Hope there's a fix for this soon. 

  8. 9 hours ago, NathanC said:

    Hi @dantaylr,

    Unlike regular groups, constraints groups will clip content off that exceeds the area of the bounding box which is defined by the nodes. As such, strokes aligned to the outside/centre exceed the bounding box, and causes the area to get clipped. This is logged with the developers to be improved so that objects inside a constraints group can exceed the bounding box, similar to a standard group. I've bumped the existing Improvement with your report.

    Thank you Nathan, I appreciate the explanation and that makes sense. It'd definitely be a great improvement as the behavior is unintuitive from the other side of the fence 😄

×
×
  • Create New...

Important Information

Terms of Use | Privacy Policy | Guidelines | We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.