There seems to be no shortage of bugs that “should have been obvious” and subject to the “how can you not check that your own products work together” phenomenon. Just the other day, I stumbled on another one. This time, it was the Microsoft set of applications and operating systems that do not quite work together the way you would expect them to.
For a while now, I have had the issue that I could not open Excel sheets (files) by double-clicking them in the Windows Explorer, nor could I directly open Excel sheets sent to me in email from within Outlook. I got an error like this: “Cannot find the file path (or one of its components). Make sure the path and file name are correct and that all required libraries are available.”
Turned out this is a fairly common problem, with a documented solution.
This is a short note about an “aha” moment: ArsTechnica just explained why Excel 2007 windows that look like being documents are not quite that, and how I sometimes manage to start multiple Excel processes by mistake. It seems that Excel is not truly a multi-window app like Word is… but still an MDI app that fakes windows in a way that makes the Windows task bar and Vista task switcher fairly confused. Thanks for the explanation.
It is a symptom of bad UI design when things just happen, and you have no why, and no visible indication to help you figure it out. Last night, I noted that the text in Outlook when composing email suddenly was way larger than normal. I put that way as a fluke, but today, the effect was still there, all the time. Strange. So I went in and checked my font settings, which were all fine. This being Office 2007, I suspected some kind of zoom effect, but there was no zoom indicator in any Outlook window. I tried ctrl-+ and ctrl– to see if Outlook respected the web-style view size shortcuts. But no effect.
I work quite a lot with Wikipedia systems (mostly mediawiki-based) to structure data and make it accessible to other people at my job. Since I happen to love tables as a way to provide overviews and summaries of complex information, I keep creating wiki tables. Editing tables in a wiki is pretty painful, especially when it is time to do things like add columns. Excel is a much superior tool for this purpose, and I have been looking for a tool to let me create tables in Excel and then get a wiki rendering of them for insertion into a wiki. Finally, I have found it! Here, you can find a pretty good Excel VBA macro that lets you select a range of cells and then get a wiki table code corresponding to it on your clipboard, ready to paste into the wiki site. Thanks a million times to the creators of that tool, it is really useful. Note that in Office 2007, you must save documents in .xlsm, macro-enabled, format to be able to save the macro with your file.
I finally switched to Microsoft Office 2007 in June this year. I was very hesitant, but I have been very pleasantly surprised by how well the new GUI works and how easy it is to get things done – once I stop trying to do things in the old way of Word.
But every once in a while, you get totally stumped trying to do something that was dead easy in “old” Word versions. Once such instance was a colleague of mine totally failing to figure out how to number the headings in the document. Which is pretty standard in technical writing. It took me a while, but I did figure it out. As I could not find any good link on the web explaining how to do this, here is my take that I hope some other desperate soul can search for and find.
One common use-case for multicore processing on the desktop and elsewhere is “doing many things at the same time”. You could be running many user-interface programs at once, like the “typical today’s teenager template” of tens of IM clients, web sessions, email conversations, music and video players, downloading movies, etc. Or it is a more business-like background indexing of harddrives, backups being taken, downloading large business files, compiling software, updating source code repositories, etc.
I have been doing both of these modes to some extent, and the main problem with them at least on a PC is that while the processors might be good at multitasking and sharing the CPU load, my IO system is annoyingly non-parallel.