AlisterH
AlisterH
"Lines to Polygon" also produces an error if there is a line that starts and ends at the same point. I note that the "native" (built in) QGIS "lines to...
Ah, yes, it seems it doesn't error with **_every_** "line that starts and ends at the same point". But here is an example. [example9.zip](https://github.com/LEOXINGU/lftools/files/15157148/example9.zip)
I note also that it generally doesn't join lines which would form (or already are) a feature with two vertexes at the same point (except if it is the start...
Could the problem be that people are using `--empty` to merge files easily, not realising that it throws this information away? ```` qpdf --empty --pages Contents.pdf empty_A4.pdf -- out.pdf qpdf...
Note that paperjam (which uses libqpdf) also has this function.
I don't know enough to comment other than that as a user there is a continuum of behaviour from most to least preferrable, something like this: - Implement full support...
Also, even when calculations are being updated, often the display of line# references isn't updated.
Sometimes I see this too: ```` ERROR:com.github.parnold_x.nasc.p/src/Controller.c:1704:string_replace: code should not be reached Bail out! ERROR:com.github.parnold_x.nasc.p/src/Controller.c:1704:string_replace: code should not be reached
OK, I've confirmed that "running on Windows 10 with WSL" is not a factor, as I can reproduce it in nixOS running on bare metal.
> I would add that no text edition is saved in the file. After saving the changes or creating a new file with the changes, the text remains the same...