Office X & long file names
October 22, 2002 12:16PM
edited January 2014
Why hasn't Microshaft patched this stupid problem, where we can't create files with names longer than 32 characters? Does anyone know if they plan to fix this?!
Reply 1 of 5
October 22, 2002 12:47PM
I believe they will do that in the next version of Office. They claim that it is actually quite hard to do with Office's legacy code.
Reply 2 of 5
October 22, 2002 7:00PM
For what they charge, that's a joke. Good thing it's easy to copy. Keep that up, M$, that's a feature I actually use
Reply 3 of 5
October 25, 2002 3:07PM
have to wait for the next Office for long filenames? :eek:
Reply 4 of 5
October 25, 2002 3:36PM
[quote]Originally posted by Aquatic:
have to wait for the next Office for long filenames? :eek: </strong><hr></blockquote>Yeah. Pathetic, huh?
And they wonder why so many people pirate Office. Gee, Microsoft, don't do a half-assed job. Release a quality product and people might be more willing to shell out some cash.
<img src="graemlins/oyvey.gif" border="0" alt="[No]" />
If I recall correctly, the code for supporting long filenames has been around since 1999.
Andrew Welch (aka. moki) showed a little tutorial on MacNN a year or more ago on how easy it was to change the old calls to the new ones. It looked pretty simple to me, at least... though, Microsoft probably has millions of lines of crufty old code to wade thought to find it all.
Reply 5 of 5
October 26, 2002 4:59PM
There's always time to redo icons though!
Seriously the icons are less recognizable even though they're prettier. I think the more realistic icons are the longer it takes to recognize them; I've read about how many people don't like this ability of OS X to make insanely large and detailed icons. It's a trade-off to me: looking cool or being functional. As we all know Apple usually chooses the former!
Yes I bet Office has incredibly ugly code. Is the next Office going to be Cocoa, Carbon, a re-write, does anyone know?