Staff Ben Posted September 29, 2016 Staff Share Posted September 29, 2016 @Herojas93 I emailed you back a modified document. We have two kinds of layers - Logical and Physical. Logical layers are shown as either "Layers" or "Groups" in the Layers panel. Everything else is a physical layer (one that contributes something to the image). As a general rule - Always try to make outer physical objects the parent of anything contained by them on the spread. This enables a more efficient bounds calculation because it only needs to work with the outer shape. Text objects especially should be children of an outer physical layer where possible. So, for example, if text sits in front of a rectangle, and the rectangle won't clip the text geometry - make that text a child of the rectangle. nravenlock 1 SerifLabs team - Affinity Developer Software engineer - Photographer - Guitarist - Philosopher iMac 27" Retina 5K (Late 2015), 4.0GHz i7, AMD Radeon R9 M395 MacBook (Early 2015), 1.3GHz Core M, Intel HD 5300 iPad Pro 10.5", 256GB Link to comment Share on other sites More sharing options...
Staff Ben Posted September 29, 2016 Staff Share Posted September 29, 2016 Another tip - it's better to use "Groups" than "Layers" when creating symbols or assets as it enables you to select the entire symbol when clicking on spread. "Layers" click through, and so you will select one of the child layers, and not the whole layer. In a UI prototyping situation, you'd want to be able to easily select the whole object and move/snap it. "Layers" currently do not pass through for snapping bounding box calculations. Anything in a "Layer" will currently not get added to snapping when using the "Immediate layers" option. I'm in two minds as how this should work. It's not really a bug, more a question of expectations. I'm thinking that I might change it so they behave as "Groups" for the purpose of snapping. Guess we'll have to see how this pans out when people use it. nravenlock and paolo.limoncelli 2 SerifLabs team - Affinity Developer Software engineer - Photographer - Guitarist - Philosopher iMac 27" Retina 5K (Late 2015), 4.0GHz i7, AMD Radeon R9 M395 MacBook (Early 2015), 1.3GHz Core M, Intel HD 5300 iPad Pro 10.5", 256GB Link to comment Share on other sites More sharing options...
Herojas93 Posted September 29, 2016 Author Share Posted September 29, 2016 OK I'm seeing it. Now I understand. I was thinking just the oposite. The layers better than groups. I was thinking that layers can be understand as a block y AutoCad and group as a set of items (worst to select and modify). Now I have clear the concept and I will update my designs. Many thanks for your time. Link to comment Share on other sites More sharing options...
Recommended Posts