Hatch gets unwanted aditional points

Hi!

Editing non-associative hatches by their (triangular) midpoint grips leads to aditional points and therefore corners.
This behavior seems to be new in BricsCAD Version 25.2.07 and does not always occur. But I can reproduce the error as follows.

I start with a rectangular hatching and pull the lower midpoint grip further down. Then I undo the change. Now I pull the same grip down again and an additional corner point appeared at the left side of the hatching.

Does anyone get the same result or is it just me?

I can't report this bug (if it is one) via support request because I don't have an active maintenance contract.

used BricsCAD: 25.2.07-2 German
System: Windows 11 Version 10.0.26100 Build 26100

Comments

  • Hello.

    I couldn't reproduce the issue from scratch.

    There could be something particular about the hatch you use.

    You could check whether the issue occur with any hatch.

    Also, it might help to check the polyline created with the _HATCHGENERATEBOUNDARY command, to see if there is anything particular with it.

  • Hi Virgil!

    Thank you for the answer.

    That is interesting. When I proceed as described above, the error occurs every time.
    It doesn't matter if I create a new hatch from a rectangle or cut an existing hatch using _TRIM.
    And whether I create a new empty drawing or work in a large file.

    But I have noticed that the error does not always occur when manipulating the lower midpoint grip, but sometimes also at the upper or any other. Depending on how I have drawn the surrounding rectangle to create the hatch before.
    I have used _HATCHGENERATEBOUNDARY. I noticed that the additional corner point always appears where the polyline created with _HATCHGENERATEBOUNDARY has its starting point. Otherwise the polyline seems to have no abnormalities.

    The whole thing doesn't cause me big problems but it's a strange behavior of the new bricscad version I wanted to report.

  • Hello.
    Thank you for the new details.
    The issue can be reproduced.
    I reported it to the development team.