there were many discussion on that... i.e.
https://forum.freecadweb.org/viewtopic.php?f=3&t=34213
unfortunately it seems that it is not easy to get a common consensual approach
there were many discussion on that... i.e.
I agree that collaboration is difficult, but as said wasting efforts is a bad thing.
I consider measuring as a separate function from designing or drawing. The main time I measure is when I have imported a step file or opened someone’s assembly file and I’m measuring between parts so a continuous output of numbers the rest of the time is not needed, and an add-on was fine with me. Docking QM or a similar tool permanently IMO would be a waste of screen space.Saturn wrote: ↑Fri Dec 30, 2022 12:05 pm The Quick Measure workbench works exactly as I envisioned for this feature, although it does take 1 more click than the always-active feature from this post. 1 click is really a minor inconvenience for taking a measurement though.
Automatically showing measurements has the downside that is sometimes takes a long time to compute values (it seems volumes for compound solids are problematic, I might have to disable that altogether). So the approch taken by the Quick Measure WB makes sense in this regard.
+1 clic is an inconvenient IMO, such tool is very useful and often used, the more the use the more the clics.
Sure, so maybe you should delete measurement features which are too CPU consuming. Or add an additional shortcut to lauch the complex part of the measurement? So that th user will decide to get or not full measurements informations.Automatically showing measurements has the downside that is sometimes takes a long time to compute values (it seems volumes for compound solids are problematic, I might have to disable that altogether). So the approch taken by the Quick Measure WB makes sense in this regard.
IMO panel menu for existing measurements tools are great, but it clutters the screen and requiere to download addons and/or load WB. Not so easy for beginers.I might take a look at how easy it would be to port the Quick Measure code to C++ then that might result in a feature that requires less clicks and window real estate than the current Quick Measure workbench.
Another option would be to tweak the Quick Measure tool to allow docking the measurement window permanently. That would be a straight forward approach if the goal is primarily to reduce effort needed for taking measurements.
Code: Select all
print(obj.Shape.Edges[7].Curve)
Circle (Radius : 2.675, Position : (0, 1.90348e-15, 8.5725), Direction : (-0, 2.22045e-16, 1))
IMO not the best:
Are you sure about that? I hope I get you right, but AFAIK now element information is displayed in status bar when mouse cursor spend over elements, no any selection is needed or even efficient.Now the behavior (0.20.2) is that when you select something you will have in the statusbar these informations:
How many times you want a complete info about an object regarding measurement, not every time you select them. so carpal tunnel is not a problem at least in this case.
In fact, only when I select explicitly an element additional infomation should be displayed, not to overload FC when not needed to measure thing, but this is a personal preference.-alex- wrote: ↑Fri Jan 06, 2023 4:39 pm ...
Are you sur about that, as I can see now element informations are displayed when mouse cursor spend over elements, no any selection is needed. I hope I get you right?
So that those element informations could be temporily overwrite by measure informations, just when elements are selected?
Main dimensions for a circle "radius, center" are the data you need to know for a line, length and probably start and ending point.-alex- wrote: ↑Fri Jan 06, 2023 4:39 pm In some big CADs such measurement text informations at first sight provide only mains dimensions, not too much informations.
Type of elements is even not mentioned: if you read ... In progress
IMO that is the good aproach. If the user want more mesurment informations he has to use a more specialized tool, like existing mesurement tools in addon manager or in some WB.
When a user makes a circle and another feature touches the circle it will create two arcs. I found it hard to determine arcs from circles.
I don't use scripting to model parts so I never considered that.