<br><br><div class="gmail_quote">On Thu, May 5, 2011 at 9:24 PM, Alastair M. Robinson <span dir="ltr"><<a href="mailto:blackfive@fakenhamweb.co.uk">blackfive@fakenhamweb.co.uk</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"> Hi,<div class="im"><br> <br> On 05/05/11 16:32, Chris Murphy wrote:<br> <br> <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"> If a single application cannot be produced to do this correctly and<br> reliably, we certainly have the very same problem with it in a CPD that<br> then all applications are subject to with no other (simple) means of<br> working around it. I think that's a problem.<br> </blockquote> <br></div> What strikes me is that if it's impossible to do pass-through-colour using the CPD then our standalone target-printing application has to bypass the CPD completely. It effectively has to implement a separate printing path, and can't leverage the CPDs setting of options, job tickets, etc., and the chances of keeping that application maintained and "in sync" with the CPD are pretty slim.<br> </blockquote><div><br></div><div>The only way one can guarantee that code stays in sync across apps is to have a unique codebase. </div><div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"> <br> Having a CPD flag that applications use to signal that "advanced" options should be shown would be just about tolerable, I suppose, but still seems like needlessly sacrificing functionality on the altar of user-friendliness to me. (And we see so much of that these days that some of us, myself included, are admittedly hyper-sensitive and quick to shout if we see any hint of it happening!)<br> <br> All the best<br> --<br><font color="#888888"> Alastair M. Robinson</font><div><div></div><div class="h5"><br> _______________________________________________<br> openicc mailing list<br> <a href="mailto:openicc@lists.freedesktop.org" target="_blank">openicc@lists.freedesktop.org</a><br> <a href="http://lists.freedesktop.org/mailman/listinfo/openicc" target="_blank">http://lists.freedesktop.org/mailman/listinfo/openicc</a><br> </div></div></blockquote></div><br>