- Subscribe to RSS Feed
- Mark as New
- Mark as Read
- Bookmark
- Subscribe
- Printer Friendly Page
- Notify Moderator
Attaching a macro as a user asset doesn't respect Relative dependencies
- Subscribe to RSS Feed
- Mark as New
- Mark as Read
- Bookmark
- Subscribe
- Printer Friendly Page
- Notify Moderator
I frequently have to build nested macros into workflows that will live on the Gallery. Unfortunately, Gallery does not "see" these nested macros when I save to Gallery and manage assets. I have to open the macros, attach the nested macros within through every single nesting layer, save all of them, then return to the main workflow before I can save to the Gallery and have it "see" the nested macros. I usually attach them to the workflow so I don't have to check them on in the Gallery menu anyway. That's why I have to attach the nested macros.
Anyway, when I change all dependencies to relative, these nested macros are not showing that they have relative paths. I cannot get that to work, try as I might. That makes this problematic for version control. How can I attach macros using relative dependencies?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.