When Japanese is the default editing language, PowerPoint has an UI option to apply Japanese-language text rotation, which rotates letters and digits differently . However, this property seems missing from the object model and an add-in therefore cannot know its state. Therefore, the add-in is bound to handle such text incorrectly.

Apply the rotation setting from scratch:
1) PowerPoint > File > Options > Language > Choose Editing Languages > Japanese (set as default) > OK
2) Restart PowerPoint
3) Create new empty file
4) Insert textbox
5) In textbox, write test123
6) Select textbox
7) PowerPoint > Home > Paragraph > Text Direction > Vertical
8) Save file

RESULT:
The text is rotated such that "test" is rotated 90 degrees clockwise, while the digits "123" are not rotated.

9) Rename the resulting file to *.zip and unzip it. Navigate to ppt\slides and open slide1.xml. The associated XML property seems to be "kumimoji": <a:endParaRPr lang="ja-JP" altLang="en-US" kumimoji="1"/>

Compare the definition in the ECMA Office OpenXML - Fundamentals and Markup Language Reference:
"Kumimoji specifies whether the numbers contained within vertical text continue vertically with the text or whether they are to be displayed horizontally while the surrounding characters continue in a vertical fashion." (e.g., section 21.1.2.3.2 defRPr (Default Text Run Properties)).

It should be possible for an add-in to check if a text run's properties contain this setting and to change it.

Preferably, the PowerPoint programming API for Mac should behave the same as PowerPoint for Windows.

In PowerPoint for Windows, clicking into the thumbnail pane generates WindowSelectionChange events.

However, in PowerPoint for Mac (tested: Office 2016 Insider Slow Version 16.8 (Build 171210) and also Insider Fast, clicking into the thumbnail pane DOES NOT generate WindowSelectionChange events. Changing the selected slide in the thumbnail pane does NOT generate WindowSelectionChange events either.

(Note that in Mac Office v16, the WindowSelectionChange event DOES fire for other selection changes, which was a new addtion to v16. It's just that it is missing for the selection change in the thumbnail pane)

This means that an add-in cannot correctly react to such selection changes on the Mac. E.g., the add-in's buttons may stay clickable although this is not appropriate.

PowerPoint chart filter shows "The linked file is not available" when the filter is clicked for the second time.

When troubleshooting the issue found out the cause as Excel VSTO Add-in which handles "ApplicationWorkbookOpen" Event in ThisAddin.vb. Even without any code in "ApplicationWorkbookOpen" causes this error. If I comment 'Application_WorkbookOpen' then it works fine.

This happens for other Workbook events as well.

Posted the same issue with a sample excel add-in in msdn fourm. Please go through for more information.

https://social.msdn.microsoft.com/Forums/vstudio/en-US/7650df3d-3b60-4598-93ff-4730c945babb/powerpoint-2016-chart-filter-issue?forum=vsto

Our add-in is deployed for more that 5000 users globally. It will be great if this issue is fixed.

During the slide show (presentation mode), it would be great if the user was able to click buttons. This worked until some weeks ago, but now I am not able to click buttons during presentations on my Laptop (Lenovo Thinkpad E540). The presentation will just jump to the next slide, thus the app is not focused. But this still works on my colleague's laptop (Asus Vivobook S400C).

Is this an intended change or will users be able to click buttons in PowerPoint content apps in the future?

Lenovo Laptop PowerPoint Version: 16.0.7726.1042 (64 Bit)
Asus Laptop Powerpoint Version: 16.0.8201.2102 (32 Bit)

The current PowerPoint capabilities for inserting text/images is very limited and it would be nice to be able to interact with the elements on a slide.

My specific scenario is to move an old VSTO plugin over to the add-in model, where I iterate all text elements, and change the language of the text boxes. It's very common in Europe that the template is either in the native language or English, and content is then opposite of the template. A link to the VSTO can be found at https://officeaddin.codeplex.com/.

If adding direct slide capabilities is a stretch, then a possibly quicker route is to enabled Office.CoercionType.Ooxml for PowerPoint as it is for Word. This way we could parse and manipulate the data ourselves.