WindowSelectionChange event bug

Question

Hi all,

I've found a(nother) bug in PowerPoint 2007 / VBA.  If you set up an event class the WindowSelectionChange event does not fire consitently when you select different single cells in a table.  Specifically (this will make you chuckle), if you place the cursor at the same character position in the newly selected cell as the character position of the cursor in the previously selected cell then the event doesn't fire!

Example 1:

If you have the cursor in Cell(2,3), after the 3rd character, then place the cursor in Cell(4,5) after the 3rd character, the event does not fire.

Example 2:

If you have the cursor in Cell(2,3), and there isn't any text in that cell, then place the cursor in Cell(4,5) where also there is not text, because the cursor is at character 0 in both cells the event does not fire.

I find this behaviour also occurs when you select the whole cell, if both cells contain the same number of characters (or both cells are empty).

Has anyone else found this (or more importantly NOT found this)?

Does the same thing happen in 2010 (or 2013!)?  If so, can we get this reported as a bug to MS?

Cheers

Rich

Answer 1

Rich,

We can usually help get demonstrable/reproducible bugs in front of the right set of eyes, especially if we have a good description (like the one you've already supplied) and some files/code that demonstrates the problem. 

IOW, shoot me a sample file and copy/paste your description from here into the body of the email.  I'll test for repro and cast it on into the mouth of the beast.

steve at pptools dot com

Answer 2

Hi Hans,

Thanks for confirming that it's still there in 2010.  Never in a million years do I expect MS to fix this in time for the release of 2013, but (if it is still a bug in 2013) it would be nice if it made it into a service pack, or failing that they might fix it in time for 2016!  Then again, it would be even nicer if they've already sorted out the OM for Tables (and Charts) in PowerPoint 2013, so for example, we'd be able to work with a Selection object that represents a range of cells.... but I'm not holding my breath.

In the mean time... I don't suppose anyone has a work-around?

Oh, an what is the best way to report a bug like this?  I read on here once that MVPs sometimes have "special channels"...

Cheers

Rich

Answer 3

PowerPoint 2010 exhibits the same behavior; I doubt Microsoft will be willing to correct this now that Office 2013 has been RTMed. I don't have PowerPoint 2013 yet.