The ultimate fix to my concern here will be to move to a memory device driver,
but for right now I am trying to distract myself from that and get some much
needed work done (small grant proposal). The question is one of design in my
Smalltalk binding: how should it work? How can it work?
One
Schwab,Wilhelm K wrote:
> The ultimate fix to my concern here will be to move to a memory device
> driver, but for right now I am trying to distract myself from that and get
> some much needed work done (small grant proposal). The question is one of
> design in my Smalltalk binding: how should
On 2010-09-18 16:10-0400 Hezekiah M. Carty wrote:
> Those all look like good changes [to pllegend] to me as well. I haven't had a
> chance to look in detail at the factor of 0.5, but I didn't see
> anything obvious in my brief scan through the code.
>
> My main question about the API changes you
Hi again, Hez:
On 2010-09-25 15:32-0700 Alan W. Irwin wrote:
> Once the pllegend API includes cmap1 and is therefore complete, I hope
> you will review it, but meanwhile your preliminary review of the
> current part of the API that excludes cmap1 functionality would be
> quite useful as well. For
On 2010-09-25 15:32-0700 Alan W. Irwin wrote:
> I hope to finish all the remaining implementation of the current
> pllegend API later today
DONE as of revision 11219.
I have now tested everything related to line-, symbol-, and
cmap0-style legends as well as PL_LEGEND_TEXT_LEFT, and everything
lo
