Hi Jim
>
>> I personally am a bit uncomfortable with the way plbuf_bop() calls
>> wr_command(). Although I can see the code reuse benefits somehow it
>> feels wrong that we start generating sub commands within commands and
>> I can't quite put my finger on why it feels wrong. Perhaps someone
>> el
values, then on replot it must reinstate them and call the
>>>> appropriate
>>>> functions so the state gets passed to the driver.
>>>>
>>>> The only alternative is to reset all state parameters to their defaults on
>>>> bop. This
t;> bop. This would break most of our examples and most user code I imagine (it
>>> would certainly break all mine).
>>>
>>> So in summary, this bug has even more complex and likely repercussions than
>>> you mention in your message, but the fix is pretty stra
their defaults on
>> bop. This would break most of our examples and most user code I imagine (it
>> would certainly break all mine).
>>
>> So in summary, this bug has even more complex and likely repercussions than
>> you mention in your message, but the fix is prett
> Phil
> ________
> From: Jim Dishaw
> Sent: 05/03/2015 04:20
> To: Phil Rosenberg
> Subject: Re: [Plplot-devel] buffer state parameters
>
> I think I tracked down the bug and it might be tricky. I noticed that when
> I put a pladv(0) before chang
Okay
I will leave that with you then
Thanks
Phil
On 4 March 2015 at 15:07, Jim Dishaw wrote:
>
>> On Mar 4, 2015, at 9:13 AM, Phil Rosenberg wrote:
>>
>> Hi Jim
>> There is still a bug in the buffer with respect to the correct state
>> parameters. I think we discussed this in the past regarding
> On Mar 4, 2015, at 9:13 AM, Phil Rosenberg wrote:
>
> Hi Jim
> There is still a bug in the buffer with respect to the correct state
> parameters. I think we discussed this in the past regarding plplot
> initialisation, but this particular bug occurs at page change.
>
> Basically at the beginn
Hi Jim
There is still a bug in the buffer with respect to the correct state
parameters. I think we discussed this in the past regarding plplot
initialisation, but this particular bug occurs at page change.
Basically at the beginning of a render, plplot inherits it's state
from the previous render
