<div dir="ltr"><div><br></div><div><br></div><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Jan 13, 2016 at 10:13 AM, jmh530 via Digitalmars-d-learn <span dir="ltr"><<a href="mailto:digitalmars-d-learn@puremagic.com" target="_blank">digitalmars-d-learn@puremagic.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><span class="">On Tuesday, 12 January 2016 at 21:48:39 UTC, Per Nordlöw wrote:<br>
</span><span class=""><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
Have anybody been thinking about adding a scale-hierarchy structure on top of ndslice?<br>
</blockquote>
<br></span>
What is a scale-hierarchy structure?<br>
</blockquote></div><div class="gmail_extra"><br></div><a href="https://en.wikipedia.org/wiki/Mipmap">https://en.wikipedia.org/wiki/Mipmap</a><br></div><div class="gmail_extra"><br></div><div class="gmail_extra">but isn't it out of scope? </div><div class="gmail_extra">Looks like it would belong more to an image processing library (building on top of ndslice)</div><div><br></div></div>