View Issue Details
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0000704||GCS||General||public||2012-05-15 18:30||2021-02-06 06:31|
|Platform||32 bit||OS||Win7||OS Version||latest unstable|
|Summary||0000704: Sketcher Fully constrained report based on primitives (Lines, arcs)|
I do not know if this makes sense, but I know it was mentioned before somewhere.
It would be nice that "fully constrained" report is based on single lines/arcs, and not on entire sketch. This way it would be easier to identify which parts of a sketch are not fully constrained.
Maybe it would be useful to make lines display in a constrained color and an unconstrained color individually, rsther than making the entire sketch change to the constrained color when all degrees of freedom are removed.
It can be difficult to find the last unconstrained elements of a complex sketch.
||That is exactly what I ment. Would be very nice.|
Also, it would be nice if overconstrained primitives would be drawn in red (or some other color that is not used and that will mark over-constrained primitive)
EDIT: OR, even better, change color of conflicting constraints, so that user sees them on screen, selects one he does not need, delete it and be done with it.
maybe pink/purple color for conflicting constraints can be good. I'm bad with colors chosing. Really bad.
Reminder sent to: logari81
@logari81 should this be tagged 'Solver'
@trampas writes in 0002653
||This seems as a simple solution to a problem that is easy to run into in FreeCAD - I have used FreeCAD intensely in periods (creating objects to 3D-print) and still "hit" this, and I get as baffled every time.|
As for showing fully constrained elements, the problem is as in here:
As for getting functionality to identify where the dossier is not yet constraint, the recently merged DoF Finder should help, just click on the hyperlink of the DoFs.
||As with 0002069, what is not implemented is constantly adapting the colors. This is not happening in v0.18, as complex sketches would have a significant drop in performance due to constraintly solving using the DenseQR algorithm.|
||This ticket has been migrated to GitHub as issue 5554.|
|2012-05-15 18:30||pperisin||New Issue|
|2012-05-16 22:45||djreichel||Note Added: 0002055|
|2012-05-17 06:18||pperisin||Note Added: 0002056|
|2012-06-05 12:11||logari81||Status||new => assigned|
|2012-06-05 12:11||logari81||Assigned To||=> logari81|
|2012-06-05 12:23||pperisin||Note Added: 0002131|
|2012-06-05 12:24||pperisin||Note Edited: 0002131|
|2012-06-05 12:34||pperisin||Note Edited: 0002131|
|2012-12-20 22:06||logari81||Project||FreeCAD => Sketcher|
|2013-03-08 20:04||logari81||Relationship added||has duplicate 0001041|
|2015-04-26 18:32||normandc||Relationship added||has duplicate 0002069|
|2017-01-18 22:10||Kunda1||Note Added: 0007867|
|2017-04-02 08:55||kkremitzki||Assigned To||logari81 =>|
|2017-04-02 08:55||kkremitzki||Status||assigned => new|
|2017-05-02 21:22||Kunda1||Tag Attached: Solver|
|2017-05-02 21:22||Kunda1||Status||new => confirmed|
|2017-06-16 11:46||Kunda1||Tag Attached: constraints|
|2017-06-16 11:51||Kunda1||Note Added: 0009406|
|2017-06-27 15:40||Hannu||Note Added: 0009565|
|2017-12-13 15:20||Kunda1||Project||Sketcher => GCS|
|2018-06-15 17:02||abdullah||Note Added: 0011444|
|2018-06-15 17:02||abdullah||Assigned To||=> abdullah|
|2018-06-15 17:02||abdullah||Status||confirmed => assigned|
|2018-10-06 15:37||abdullah||Category||Feature => General|
|2018-10-06 15:37||abdullah||Target Version||=> 0.18|
|2018-10-07 11:05||abdullah||Note Added: 0011956|
|2018-10-07 11:05||abdullah||Target Version||0.18 => 0.19|
|2020-11-10 12:56||abdullah||Target Version||0.19 => 0.20|
|2021-02-06 06:31||abdullah||Target Version||=> 0.20|