Hi,
The setting for the lower case caps is not accepting 100%. Is this intended as it would basically mean everything is in capital letters ?
Hi,
The setting for the lower case caps is not accepting 100%. Is this intended as it would basically mean everything is in capital letters ?
Hi -
The developer spent quite a bit of time looking through the code that is involved here. We have passed SDK freeze for Rhino 8 and changing how this works seems to require deeply-rooted changes to that SDK. Making it possible to enter 100% in that field will go on the 9-list.
For the time being, you’ll have to either use 99% or, e.g., copy the string into the Text
dialog and use the Uppercase button to make it all-caps.
-wim
Thanks for the update.
My main concern was that the field accepts three digits when typing, but truncates the number afterwards. So it’s more UI related.
I agree that setting all caps should be the correct way to set the entire text to caps.
I am puzzled as to why one might want to do that though…
-Pascal
You write something with only the first letter of each word as a cap.
It doesn’t look great, you want to try it with full caps…
If you use the Uppercase you lose the ability to revert to the original text.
(that’s what I did, I ended up doing the text manipulation in MS Word).
Yes, but why would one want to do 99%? Or 85%? Where’s the line?
Should it allow 200%?
I guess I’ll just write up a request to have the same “case” buttons available as they are on the regular Text
dialog:
EDIT: Actually, they are already available
-wim
I thought about it
They are already. The solution is simply : don’t let more than two digits be entered in that numeric field when typing.
And change “small” to “scaled” so it makes sense