<html><head><meta http-equiv="Content-Type" content="text/html charset=windows-1252"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"><br><div><div>On 25 Aug 2014, at 23:48, Maximilian Bareis <<a href="mailto:max.bareis@me.com">max.bareis@me.com</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"><div><div><blockquote type="cite"><div style="font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;"><br></div></blockquote><div>as I answered to Esteban, the creation of SVGAnchor depends on the state of the context. If the context has the state disableSVGAnchor the disabledAnchor is created otherwise the SVGAnchor is created. Why the disabled state is coupled to the context is beyond my knowledge, this needs to be answered by Johan or the creator of SVGCanvas>>anchor: </div></div></div></div></blockquote><div><br></div><div><div>I’m not the creator of the package and it’s been some years ago I actually looked at its code.</div><div>From looking at the code, it seems the anchors are being disabled when the svg is being exported to a file. </div><div><br></div><div>I’m not sure if this is a technical requirement or a convenience to prevent urls from a seaside app being exported to a file (which does not make sense).</div><div><br></div><div>If Holger (the original author) is still following this list, he might be able to comment…</div></div><br><blockquote type="cite"><div style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"><div><div><div>If you think you do not need this feature in WABuilder I will subclass it to SVGBuilder.</div></div></div></div></blockquote><div><br></div>I’m not sure. You should have access to the renderContext from within your test and set the disabledAnchor flag without changing code to WABuilder.</div><div><br></div><div>I don’t understand the necessity to add an ability to put in your own rendercontext because:</div><div>- you are still using a WARenderContext instance</div><div>- you can manipulate the instance after constructing it:</div><div><br></div><div><div><span class="Apple-tab-span" style="white-space:pre"> </span>WAHtmlCanvas builder render: [ :html |</div><div><span class="Apple-tab-span" style="white-space:pre"> </span>html context disableSVGAnchors: true.</div><div><span class="Apple-tab-span" style="white-space:pre"> </span>….]</div><div><br></div><div>Would the above not be sufficient (and avoid other refactorings?)</div><div><br></div><div>Johan</div></div></body></html>