Why does the blinking I-beam cursor keep disappearing when editing text inside tables in Word 2011?

Hi Pierre:

Well, the problem doesn't reproduce on this machine.

It would depend very much on your hardware as well as the complexity of the document.

Certain models of graphics card are more likely to do it than others: more powerful hardware recovers quicker, better-structured documents put less load on the hardware.

But you're right: Microsoft's not going to spend money on this one just months before the next version comes out.

Cheers

A 2014 Mac Pro ought to be more than enough power, but in any case, the visibility of the cursor should be an absolute priority and should not depend on the graphics card, the hardware, the complexity of the document, etc.

We're talking about basic stuff here, for which there is no excuse if you screw up, which Microsoft repeatedly does.

And I am also willing to be $500 that the problem will still be there in the next version of Office.

Pierre Igot

--

BETALOGUE - Weblog at http://www.betalogue.com | Twitter: @betalogue

Hi Pierre,

If it makes you feel better, I also notice that on occasion that the cursor does not come up right away. It doesn't seem to happen with any regularity, and I haven't been able to nail down a specific set of steps to follow to make the problem happen consistently.

It would be great if we had a particular document that reliably exhibits the problem if we follow a specific set of steps in a given update of Word on a specific version of Mac OS X on certain macs with certain graphics cards with given amounts of RAM and nothing else is running at the time. That way we could tell Microsoft to have an engineer take a look at what's going on in the same setup and try to fix it. If the problem turns out to be something in Mac OS X, that's OK because Apple and Microsoft engineers have a good working relationship despite the marketing departments having fun with the whole rivalry thing. The Microsoft and Apple engineers do work together to smooth things out when there's a mutual bug. Microsoft also works with hardware manufacturers when necessary to smooth things out with drivers, etc.

There are significant differences in various versions of Mac OS X with regard to hardware and drivers. For example, my 1.5 yr old MacBook Pro will not connect to the internet via WIFI in Yosemite. Yet it has no problem with Mavericks. I bring this up because it suggests that if you reinstalled the same version of Mac OS X, and it turns out the problem is in that particular version of Mac OS X  on your hardware configuration, maybe wiping the drive and trying a different version of Mac OS X could clean up the problems you're having.

I believe I have made it quite clear that I have had problems with the blinking cursor in Word since version 2004, and through a variety of hardware changes and system upgrades, all the way to today, with Office 2011 on a 2014 Mac Pro and Yosemite. In light of this, it's very hard for me to believe that it might be a specific hardware/software configuration that is causing the problem.

Yes, the ultimate goal would be to find a document where the problem is irrefutably reproducible on a variety of machines. I don't have access to a variety of machines, so such an investigation would require at the very least cooperation between users and at best the collaboration of Microsoft's own team of engineers.

I am glad to hear that you are not dismissing my problems altogether, but until I see a bunch of users saying, "Yes, I have the same problem with the same document (or type of document) on my computer", I am afraid we're not going to get anywhere. 

As always, it seems that I, as the end user, am the one expected to do all the hard work of gathering the required evidence. In case this isn't obvious: I also have a job, and a life. There is only so much that I can do to help move things forward. The very fact that it's so hard to get people to take these problems seriously can be very discouraging at times.

I understand how software development works. But at the same time it would be more encouraging to see signs that Microsoft's own staff is taking things more seriously. There are just so many things that don't work right, haven't worked right for years, and are not getting fixed… including perfectly reproducible problems such as this one:

Delete inserts an extra paragraph mark

I mean, how obvious do things have to be?

Pierre Igot

--

BETALOGUE - Weblog at http://www.betalogue.com | Twitter: @betalogue

OK - but for now let's try to figure out the cursor problem. Do you (not referring just Pierre but anyone who has this problem) have a document that you can share with the world that exhibits the problem? If you do, that would be great. We (the rest of the world) can try to replicate the problem on our own Macs. If you have such a document or encounter one in the future upload it to OneDrive, DropBox or other sharing service and provide a link to it. 

If I can replicate the problem on my own Mac I'd be happy to do what I can to get someone at Microsoft to look at it,