Dashanan

My feedback

  1. 274 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    Dashanan supported this idea  · 
  2. 32 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    Dashanan supported this idea  · 
  3. 5 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    Dashanan supported this idea  · 
  4. 12 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    Dashanan commented  · 

    The work-around hack I had given previously has stopped working since Sep 2019. :-(

    Guess someone in the XD team tried to fix the issue and ended up overriding the hack. So they need to come up with a legit solution for this issue. Hopefully soon. I have mobile projects so large that the project canvas does not accommodate all the artboards - and the asset count is well over 2000. Right now have no option but to give developers all the assets separately in a ZIP. But if Adobe doesn't solve this quick, they are simply telling us to switch to Zeplin/Sympli/Avocode etc.

    Also, why has Adobe team archived the bugs section of uservoice? I know uservoice is way overpriced -but it should still fit in Adobe's budget. And the program is still nowhere near stable and bug-free. They should be want as many crowd-sourced bugs as possible.

    Dashanan commented  · 

    Okay, here's a hack to solve this problem:

    1) Open the "Share for development" menu.
    2) Uncheck the "Include assets for download" option.
    3) Tap on "Create link".
    4) The link will be created smoothly.
    5) Now open the "Share for development" menu again.
    6) Check the "Include assets for download" option.
    7) Tap on "Update" and republish the link.
    8) The link will get publish successfully - No 44:23 error! :-D
    9) Open the design specs link. All assets will be available.

    Let me know if this works for you.

    Dashanan commented  · 

    This issue seems to be caused by the overall size of the assets being exported. If the file has 1000+ assets but totalling to under 25-50 MB, then you will face no problem. However if the assets are heavy (E.g. lots of PNG files) then this issue arises. Adobe team must have set a limit to the maximum size for all assets being exported in a link. When the limit is crossed, this error occurs. I have to split my files into small chunks and then export for the design specs to work. Hope this issue will get resolved soon.

    Dashanan supported this idea  · 
  5. 6 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    Sorry to hear that you are encountering publish error while trying to update the links.

    In-order for us to understand the exact scenario, can you explain what did you mean by – “I downloaded a document and changed just the text size on 6 text boxes. I re-uploaded the document so that my colleague could create the link for development”

    1. Are you using a local or a cloud document?
    2. If it is local document, are you keeping it in a shared server from where both you and your college keep doing changes?
    3. Are you both publishing links from the same document or only one of you publish?

    Thanks!

    Dashanan commented  · 

    Okay, here's a hack to solve this problem:

    1) Open the "Share for development" menu.
    2) Uncheck the "Include assets for download" option.
    3) Tap on "Create link".
    4) The link will be created smoothly.
    5) Now open the "Share for development" menu again.
    6) Check the "Include assets for download" option.
    7) Tap on "Update" and republish the link.
    8) The link will get publish successfully - No 44:23 error! :-D
    9) Open the design specs link. All assets will be available.

    Let me know if this works for you.

    Dashanan supported this idea  · 
  6. 4 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    Hi,

    Please try the below workaround whether it is resolving “create a new share for development link”

    1. Publish new link by uncheck “include assets”
    2. Once the link creation is successful, go ahead and check “include assets” (tick mark)
    3. Update the same link

    Regards,
    Muthukumar

    Dashanan supported this idea  · 
  7. 6 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    Dashanan supported this idea  · 
  8. 19 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    8 comments  ·  Adobe XD: Feature Requests » 01 : Design mode  ·  Flag idea as inappropriate…  ·  Admin →
    Dashanan supported this idea  · 
  9. 261 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    Dashanan supported this idea  · 
  10. 19 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    4 comments  ·  Adobe XD: Feature Requests » 01 : Design mode  ·  Flag idea as inappropriate…  ·  Admin →
    Dashanan commented  · 

    @Corey... Yes, your idea for a "Drag affordance" feature would be perfect.

    Dashanan shared this idea  · 
  11. 7 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    Dashanan commented  · 

    It is common for mobile designs to have a bottom fixed navigation. However when the navigation layer is set to "Fix position when scrolling" - any layers in the body which happen to be at the bottom of the viewport get hidden by the fixed layer.

    This creates a big problem when we have to:
    1. Export the designs as PNGs for internal reviews
    2. Export to extensions like Overflow.
    3. Export design specs.

    Because in all the above cases there is no way for us to clearly see the layers beneath the fixed layers.

    As a result the stakeholder/programmers get frustrated in working with these designs.

    Example: In the attached "01 Current State... .png", the bottom nav can be seen hiding the graph layer. As a result, the stakeholders reviewing the PNG will not be able to see the graph information. Tools like Overflow will render the design with the graph hidden and no way for users to see its data. And finally the coders will have no idea how to code the graph layer in the design specs link.

    Solution:

    Shift the fixed element to the bottom of the screen, where we anyway keep an empty margin, so that the fixed elements don't hide any critical elements.

    For example, in the attached image "02 Ideal state... .png", the fixed nav bar is shifted to the bottom of the screen so that it does not obstruct any view of the elements in the body. As a result we can clearly see the graph layer without any obstruction.

    Dashanan commented  · 

    The fact that this feature has so little upvotes means that people have still never used XD for making design specs of a live project. :-(

    We don't have any way to let developers see elements hidden behind fixed-elements in the specs. This happens in case of both specs exported within XD or on Zeplin.

    Also the fixed elements feature is a pain when you want to export png of designs to share with the product team. Again the fixed elements hide everything behind them, and so the designers have to move every fixed element at the bottom of the screen and then do the export. Not fun when you have fixed elements on 50 artboards.

    XD should have simply designed the fixed element feature as in Invision. Place them at the bottom of the screen so that they don't interfere with the body of the design, while rendering perfectly in prototype mode.

    In XD we are forced to maintain two files for the same project. One for prototyping and other for design specs. Very inefficient.

    Dashanan supported this idea  · 
  12. 6 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    Dashanan supported this idea  · 
  13. 75 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    7 comments  ·  Adobe XD: Feature Requests » 01 : Design mode  ·  Flag idea as inappropriate…  ·  Admin →
    Dashanan supported this idea  · 
  14. 2 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    Dashanan supported this idea  · 
  15. 45 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    7 comments  ·  Adobe XD: Feature Requests » 01 : Design mode  ·  Flag idea as inappropriate…  ·  Admin →
    Dashanan supported this idea  · 
  16. 2,921 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    Dashanan supported this idea  · 
  17. 2,575 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    Dashanan supported this idea  · 
  18. 2 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    Dashanan shared this idea  · 
  19. 4 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    Dashanan supported this idea  · 
  20. 3 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    Dashanan supported this idea  · 
← Previous 1 3

Feedback and Knowledge Base