View Issue Details

IDProjectCategoryView StatusLast Update
0003468SketcherBugpublic2018-05-11 09:31
Reporterdrocha87 Assigned Tochrisb  
PrioritynormalSeverityminorReproducibilityalways
Status closedResolutionno change required 
Platformx64OSWindowsOS Version10
Product Version0.17 
Summary0003468: PointToPoint Constraint losing reference point
DescriptionCoincident constraint losing reference point when changed from big values to lower values.
Steps To Reproduce1) Create 2 vertical rectangles and 1 horizontal rectangle
2) Make the horizontal rectangle (corner points) symmetric to V_axis
3) Give a distance to the horizontal rectangle
4) Make a coicindent constraint between the vertical rectangles with the vertical rectangle
5) change the distance of the horizontal rectangle to big value (200mm->2000mm) and change back to (200mm)
6) As showed in the images the coincident constraint lose their initial position

Additional InformationOS: Windows 10
Word size of OS: 64-bit
Word size of FreeCAD: 64-bit
Version: 0.17.13515 (Git)
Build type: Release
Branch: releases/FreeCAD-0-17
Hash: e17b340949b75a226cc7d89989b0aa238ccfc75f
Python version: 2.7.14
Qt version: 4.8.7
Coin version: 4.0.0a
OCC version: 7.2.0
Locale: English/UnitedStates (en_US)
TagsNo tags attached.
FreeCAD Information

Activities

drocha87

2018-05-09 15:30

reporter  

fbug1.png (160,905 bytes)   
fbug1.png (160,905 bytes)   
fbug2.png (163,742 bytes)   
fbug2.png (163,742 bytes)   

abdullah

2018-05-11 09:17

manager   ~0011246

@chrisb

Could you please try to reproduce this one? I am not sure I understand it well.

chrisb

2018-05-11 09:31

developer   ~0011247

This is a wellknown behaviour. The coincident does not lose its connection, the so called vertical rectangles flip their sides. The inner vertical line becomes the outer and vice versa. This is somewhat cumbersome but it is not considered to be a bug as both solutions fulfill all the constraints. Often a different way of constraining helps to avoid this behaviour.
A forum discussion prior to opening the ticket - as required in huge letters on top of the page - would have revealed this immediately.

Issue History

Date Modified Username Field Change
2018-05-09 15:30 drocha87 New Issue
2018-05-09 15:30 drocha87 File Added: fbug1.png
2018-05-09 15:30 drocha87 File Added: fbug2.png
2018-05-11 09:17 abdullah Note Added: 0011246
2018-05-11 09:31 chrisb Note Added: 0011247
2018-05-11 09:31 chrisb Assigned To => chrisb
2018-05-11 09:31 chrisb Status new => closed
2018-05-11 09:31 chrisb Resolution open => no change required