QCAD Professional Version 3.26.1
macOS Big Sur Version 11.2.3
When I go into Dimension Tools>Tolerance and build my feature control frame, I'm getting a large gap between the diameter value and the maximum material condition symbol and between the datum C identifier and the maximum material condition symbol (See attached file).
Thank you,
Uhly-MN
[Solved] Dimension Tools>Tolerance Problem
Moderator: andrew
Forum rules
Always indicate your operating system and QCAD version.
Attach drawing files and screenshots.
Post one question per topic.
Always indicate your operating system and QCAD version.
Attach drawing files and screenshots.
Post one question per topic.
[Solved] Dimension Tools>Tolerance Problem
- Attachments
-
- Bug Dim Tol.dxf
- (177.64 KiB) Downloaded 406 times
Last edited by Uhly-MN on Fri Apr 16, 2021 1:33 am, edited 1 time in total.
Re: Dimension Tools>Tolerance Problem
Hi,
A wild guess ...
... Perhaps because the condition symbol is textual "Fgdtm" and exactly that long!?
It could be by standard, but it seems like a bug or at least ground for a feature request.
These can be reported here:
https://www.ribbonsoft.com/bugtracker/
There you'll need to have or make up an account.
Including a link to this topic is always nice. Linking back too
Regards,
CVH
A wild guess ...
... Perhaps because the condition symbol is textual "Fgdtm" and exactly that long!?
It could be by standard, but it seems like a bug or at least ground for a feature request.
These can be reported here:
https://www.ribbonsoft.com/bugtracker/
There you'll need to have or make up an account.
Including a link to this topic is always nice. Linking back too
Regards,
CVH
Re: Dimension Tools>Tolerance Problem
CVH,
Thank you for your feedback. I have created a ribbonsoft.com/bugtracker/ account for future use.
Andrew,
Thank you for reporting this as a bug and fixing the issue. Looking forward to seeing it in an upcoming release.
Regards,
Uhly-MN
Thank you for your feedback. I have created a ribbonsoft.com/bugtracker/ account for future use.
Andrew,
Thank you for reporting this as a bug and fixing the issue. Looking forward to seeing it in an upcoming release.
Regards,
Uhly-MN