<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><br class=""><div><br class=""><blockquote type="cite" class=""><div class="">On Sep 29, 2017, at 19:09 , Nicolas Cellier <<a href="mailto:nicolas.cellier.aka.nice@gmail.com" class="">nicolas.cellier.aka.nice@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class="">The canvas other than PostscriptCanvas don't use the target, they are sinks.</div></div></blockquote><br class=""></div><div>That’s only technically true, and really an oversight. All canvases write their output somewhere, be it a bitmap, native display surface or other ‘DisplayMedium'. A canvas is a filter for converting morphs to this target ‘DisplayMedium’.</div><div><br class=""></div><div>And having filter-canvases would be really cool :-)</div><div><br class=""></div><div>Marcel</div><div><br class=""></div></body></html>