Le 22/10/2019 à 03:33, Richard Kimberly Heck a écrit :
Only one way to find out...
More seriously, I think we /shoudn't/ be doing anything that accesses
buffer() before then, though there are some cases where we do. I think
there is such a case in the cut and paste code, though I'm not sure.
On 10/21/19 12:43 PM, Jean-Marc Lasgouttes wrote:
> Le 21/10/2019 à 18:13, Richard Kimberly Heck a écrit :
>>> To this end, a new method develMode() is added to the Painter
>>> class.
>>> With this commit, it is easy to see that macro template do
>>> not have a
>>> proper
Le 21/10/2019 à 18:13, Richard Kimberly Heck a écrit :
To this end, a new method develMode() is added to the Painter class.
With this commit, it is easy to see that macro template do not have a
proper buffer set!
I was thinking to try adding inset().setBuffer() to the
On 10/21/19 11:25 AM, Jean-Marc Lasgouttes wrote:
> commit 067d6dc759b819d2a40a4dea0b09736d474ddc24
> Author: Jean-Marc Lasgouttes
> Date: Mon Oct 21 16:45:03 2019 +0200
>
> Mark insets with invalid buffer() in red in devel-mode.
>
> We tend to have insets which buffer() member is
