Sweet!wandererfan wrote: ↑Fri Dec 07, 2018 1:11 pmgit commit 00e6e376c9 and git commit 99074228.
In today's FreeCAD-daily.
Sweet!wandererfan wrote: ↑Fri Dec 07, 2018 1:11 pmgit commit 00e6e376c9 and git commit 99074228.
In today's FreeCAD-daily.
So I've set the document units to Imperial Civil and tried entering an angle, but it defaults to decimal degrees. The FPO property is App::PropertyAngle...wandererfan wrote: ↑Wed Dec 05, 2018 2:52 pml/c 'm' is taken for metres, l/c 's' is taken for seconds(time), so I'm going with 'M' & 'S' for now. We're definitely getting closer:
...
Seconds are displayed using the global decimal place setting. Do you need decimal place on Seconds? Looks ugly to me, but that's just aesthetics, not functionality.
It appears the PropertyEditor data entry field for angles doesn't know about Units. The degree sign is hard coded.Joel_graff wrote: ↑Tue Dec 11, 2018 9:20 pmSo I've set the document units to Imperial Civil and tried entering an angle, but it defaults to decimal degrees. The FPO property is App::PropertyAngle...
Am I missing something?
Ok, thanks.wandererfan wrote: ↑Wed Dec 12, 2018 1:01 amIt appears the PropertyEditor data entry field for angles doesn't know about Units. The degree sign is hard coded.
Might take me a bit to figure this out
Code: Select all
"M" yylval = Quantity::AngMinute; return UNIT; // minute(Angular)
"S" yylval = Quantity::AngSecond; return UNIT; // second(Angular)
Code: Select all
"Angle::'" yylval = Quantity::AngMinute; return UNIT; // minute(Angular)
Code: Select all
"Unit_id_here" "'" yylval = Quantity::AngMinute; return UNIT; // minute(Angular)
Yeah, I was thinking of "context" as a way to distinguish 'minutes from 'feet. Should be able to figure it out from the type of unit length/feet, angle/minutes. But I didn't get into it very far.Joel_graff wrote: ↑Wed Dec 12, 2018 1:54 pmThe lexer / parser stuff is entirely foreign to me (I'm still having nightmares from coding a parser in Boost several years ago), but I feel like the solution lies in providing a 'context' for quantities so that quantity units (names / symbols) only need be unique within that context.
Ok. If you get some time to think about the problem a bit more, keep me updated - it'll give me a chance to learn something and maybe help out a bit.wandererfan wrote: ↑Wed Dec 12, 2018 4:01 pmYeah, I was thinking of "context" as a way to distinguish 'minutes from 'feet. Should be able to figure it out from the type of unit length/feet, angle/minutes. But I didn't get into it very far.
Just like fixing up an old house... Every improvement exposes more problems!wandererfan wrote: ↑Wed Dec 12, 2018 4:01 pmbut Expressions with dms don't parse, so I'll have to learn a bit about that area.
According to this https://en.wikipedia.org/wiki/Minute_and_second_of_arc, the proper symbols for arcminute and arcsecond are:
Hmmm.. The wikipedia article provides a nice dodge to the issue, I'll hand you that.wandererfan wrote: ↑Fri Dec 14, 2018 1:58 pmHow do you feel about using those as unique display symbols for ddmmss angle measurement?
We'd need to keep M&S for data entry(?) like we have "deg" as a data entry substitute for
- ° degree symbol (no key for ° Shift+Ctl+u 00b0)
or teach the world how to enter unicode from the keyboard.