Most of your observations seem to be accurate - IMO Microsoft has gummed up the works in terms of setting those values. They've implemented 2 separate methodologies determined by the View being used.
When in Normal View or Page Break Preview the "unknown" value you're referring to is an archaic throwback based on the Windows version. It is the column width in
characters, with the default being 10 characters wide. [For Row Height I believe it's
Points.]
When you enter a column width of .55 Excel 2016 interprets that as 55/100 of a character & you cannot enter anything other than numbers with or without a decimal point. Pardon my candor, but I believe that's one of the dumbest moves ever
made :-) I say archaic because it was adopted at a time when only fixed width characters were used on personal computers, so it was a constant strictly based on the design of the font being used. However, virtually nobody any longer uses fixed width
fonts. With proportional fonts there is no set character width so that measurement is worthless to most users.
However, if you switch to Page Layout View things work differently. The measurement is done in Inches (or whatever you have the Ruler Units st to): the dialog will interpret a value of .55 as 55/100 of an
inch rather than as 55/100 of a character... you don't even have to include
" or in. In fact, the tip box when you drag to adjust will display inches & pixels rather than characters & pixels while in that View.
If you agree that having to switch view in order to adjust those values is ridiculous, please use the ☺︎ at the right end of the Excel Ribbon to submit your comments. Also, you can post your opinion or vote for an existing suggestion atExcel for Mac
Bob,
VERY INSIGHTFUL reply! Thank you for the background on the measurement unit used in Excel. While I have been in the Desktop Publishing industry long enough to know fixed width characters, I did not know that Excel or other Office software adopted that method
for their measurement units. Very interesting and ridiculous at the same time, well I mean for our time in age (as you also stated).
I almost feel that Microsoft at times will port over a new application and play catch up on development. I mean this is clearly evident in these forums and the "suggestion" site where most are asking for features back from previous versions! If you want
to laugh, go from Lync to Skype for Business. Well, they have played a lot of catch up on this app so if you did you wouldn't see what I'm referring to but it was bad. It was so bad I wrote a 7-8 page documenting serious issues that prevented our company moving
to that application for business communications. That document got forwarded to the Microsoft Skype for Business engineers directly. Microsoft flew engineers out to our offices in Detroit where they sat with me going over my entire document. While some issues
were addressed, there are still many issues.
I guess I am conforming with Microsoft's issue/suggestion process and posting as many issues I can to eventually be heard. It's a shame that I have to waste my time putting in each of these but I must for sanity purposes (ha-ha). This issue is one of those
times.
Again, thank you for taking your time to explain to me what's going on. While I see where the issue lies, I would still like to see a resolution here. I don't think it will be an easy task to change the entire measurement system in this program but hopefully
this post will create movement. I may go to the suggestions page, write up something about changing the measurement system to the 21st century units of measurement and post the link here in the event other stumble on this post.