Darren, FDnC Red wrote > I'm already filtering on operator W and W* to find clipping paths and > excluding those paths. Are you saying there's an another way to determine > clipping paths that I may not be filtering out?
You seem to say that you merely throw away lines from a clipping path. That is not enough: You also have to throw away lines from there on which happen to not reside inside the clipping path area; until the clipping path operation is revoked by a matching graphic state restore operation, that is... > What I don't understand is how I could ever tell what's on top of what. > Ideally there would be a Z-order to the paths but I see no such thing. > Without such a mechanism I'm not sure how I would tell what is on top and > what is not. Did I miss the z-order operator or some such thing? What comes first is covered by what comes later. Until you play around with transparency groups, that is, which make the rules slightly more complicated. Regards, Michael -- View this message in context: http://itext-general.2136553.n4.nabble.com/How-to-determine-what-is-visible-tp4660471p4660476.html Sent from the iText - General mailing list archive at Nabble.com. ------------------------------------------------------------------------------ Comprehensive Server Monitoring with Site24x7. Monitor 10 servers for $9/Month. Get alerted through email, SMS, voice calls or mobile push notifications. Take corrective actions from your mobile device. http://p.sf.net/sfu/Zoho _______________________________________________ iText-questions mailing list iText-questions@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/itext-questions iText(R) is a registered trademark of 1T3XT BVBA. Many questions posted to this list can (and will) be answered with a reference to the iText book: http://www.itextpdf.com/book/ Please check the keywords list before you ask for examples: http://itextpdf.com/themes/keywords.php
