Please feel free to file a bug report below: https://www.qcad.org/bugtrackerGiuliano69 wrote: ↑Mon Aug 16, 2021 4:37 pmSo far, we have learnt two type of "patches" to this bug with this hatches (I believe that we must call it bug...)
Thank you!
Moderator: andrew
Please feel free to file a bug report below: https://www.qcad.org/bugtrackerGiuliano69 wrote: ↑Mon Aug 16, 2021 4:37 pmSo far, we have learnt two type of "patches" to this bug with this hatches (I believe that we must call it bug...)
Giuliano69,
You missed breaking up the HONEY hatch in 12 individual hatches.
True, and an easy fix would be a proposal script that isolates all hatches included in a drawing.Giuliano69 wrote: ↑Mon Aug 16, 2021 4:37 pm... you DO NOT know which hatch will cause a bug in QCAD.
And you will loose time finding the "bad guy" and fix it in some way...
One can't be sure of that or the latency wasn't noticeable ... or not noticed.Giuliano69 wrote: ↑Mon Aug 16, 2021 4:37 pmPlease consider also that that hatch has caused no such problem on the other program that created the drawing ...
HONEY.pat has a cloning load of 6, NET3.pat is even less with a load of 3.Giuliano69 wrote: ↑Mon Aug 16, 2021 10:04 pm-Net3 shows the same problem. So it is not a bug in THAT specific honey hatch
Correct, QCAD doesn't have to determine if you are pointing at a block with a hatch in it.Giuliano69 wrote: ↑Mon Aug 16, 2021 10:04 pmWhen double clicking and editing the hatched block ONLY, with the honey hatch, the zoom is very fast.
Can be, that needs some more investigation. It can also be the way things are, a compromise.Giuliano69 wrote: ↑Mon Aug 16, 2021 10:04 pm... but an algorithm problem, getting stuck in some situation that need investigation ...