![](https://secure.gravatar.com/avatar/5955e8e90611e77ccbfc7721b6112027.jpg?s=120&d=mm&r=g)
On 5/17/24 20:22, madiazm.eoicc@gmail.com wrote:
thanks Pablo, but this is strange [...] The strange thing is that it is only the first section that protrudes, the other sections are right (as seen in the link). Therefore it must not be the code definition, since in that case all sections should protrude... It might be a buggy code definition, but it may be only triggered by (yet unknown) special conditions.
Over the weekend I will slowly move my code to a new file with your code adding a bit everytime to try to spot the moment when I get this strange behaviour and then I will write again.
I hope you have already solved the issue, but I’m afraid this is the way testing for new bugs introduced in code works.
ps. I included the link because there is no attach option here in the online-mailing-list. Sorry if it not ok. Sorry, I no Google fan. But it is essential to provide problematic code (reduced to a minimal sample) in the messages to the list, not just the output.
Having the sample code, others can confirm that they are able to reproduce your issue. It wouldn’t be the first time for issues only arising in only on a single installation, on a single computer or on a single OS. The mailing list (at least when sending from a real email address) allows attachments up to 100kb. This may be enough for most minimal samples. I hope it helps, Pablo