Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

AEUX unable to handle stroke per sides from Figma #184

Open
waltercoots opened this issue Aug 10, 2023 · 2 comments
Open

AEUX unable to handle stroke per sides from Figma #184

waltercoots opened this issue Aug 10, 2023 · 2 comments

Comments

@waltercoots
Copy link

Describe the bug
On Figma frames and rectangles which have strokes applied to 1–3 sides, AEUX throws an error when an import is attempted.

To Reproduce
Steps to reproduce the behavior:

  1. Ensure Adobe After Effects and Figma are both open, configured properly, and that AEUX communicates normally
  2. Select a frame in Figma
  3. Apply a stroke to left, right, top, or bottom (but not all sides)
  4. Open AEUX from the Plugins menu > Development > AEUX
  5. Click the "Send selection to Ae" button
  6. Error appears in Adobe After Effects: Error: After Effects error: Unable to call "setValue" because of parameter 1. Value is undefined. Error on line: 979

Expected behavior
AEUX should import the frame, and one of the two following should happen:

  1. Lower effort. No stroke is applied, or strokes appear on all sides.
  2. Higher effort: Dash and Offset properties are calculated and applied to mimic the stroke from Figma

Screenshots
Value Undefined
Figma Setup

Desktop (please complete the following information):

  • AEUX 0.8.2
  • macOS Ventura Version 13.5 (22G74)
  • Figma Desktop App version 116.11.1 (Apple Silicon)
  • After Effects 23.5.0 Build 52

Additional context
A complex layout with many nested layers was throwing the error for me, so I narrowed this down by trial and error. I realize it's been about a year since updates have been made, but I thought I'd submit in case anyone else is having issues and might benefit from knowing this could be the cause. Thanks for all the hard work on this! Hope to see it updated.

@vmedium
Copy link
Collaborator

vmedium commented Aug 10, 2023 via email

@adithayyil
Copy link

Will this ever get fixed?? 🥲

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants