I do a lot of project management, which includes taking tons of screenshots of our apps throughout the day and emailing them to developers/business sponsors/etc. Does anyone know how to set the default picture style in Outlook 2007 so I can automatically have it add a shadow background without clicking through the ribbon bar every time?
I do this about 30-50 times a day so even a few clicks saved could add up.
Thanks,
Tom
Related
I have created a Bot and uploaded it to MS teams. I have already added the icons in the manifest.The uploaded icons appear only at the heading but not in the conversation.
I've heard this is apparently a "bug" that the relevant Microsoft team is dealing with, but, basically, you need to ALSO set the icon in the Azure portal, in your bot registration. Go to the Settings screen, and there's an option to upload an icon - you can use the same one you used in your Teams manifest of course.
Don't forget to click the "Save" button at the top of the settings screen when you're done. See example screenshot:
I forgot to add, very importantly, that this can take up to 24 hours for the change to come through, I think
I create new PowerPoint Content web add-in.
I want use add-in behind a text. For this I make for add-in "Send to back" and for text make "Bring to front". But in slide an add-in stay always on top see attached image.
Notice: in preview panel arrange works but in slide not. In slide show mode (F5) also not works.
PowerPoint version:
That's a known issue. Content Add-ins (Agaves) do not participate in the Z order within a slide.
I'm using the primary theme colours from Office UI Fabric Core, but no matter which theme I change to in Outlook Web Access my add-in colors don't change. It's constantly using the default blue.
I've tried clear browser history/cache, different users, different browsers, different machines.
When displaying an Outlook Add-in in OWA the add-in is displayed in its own sandboxed iframe (if this helps someone who knows how the dynamic theme mechanism is suppose to work).
Office UI Fabric team member here. Sorry for the incredibly long delay, I'm just now seeing questions about Fabric on SO.
This question has come up a number of other times and is a scenario we hope to address soon. I don't have a great answer for when we can enable picking up & applying specific Office client themes, but know that this is important for us to support in our own product scenarios, so I'd expect to see developments here soon. We'll be working with specific product teams to figure out the best way to handle this from a technical perspective.
That said, in the meantime, it is actually possible to load themed styles in Fabric-React today that should give you an indicator of what the solution might look like: try changing a theme color like themePrimary on this page, then view a component like Button to see that change reflected there. I imagine the solution we end up with will look similar to this.
I'm writing a PowerPoint content addin using Office.js API. I need a way
for each instance of that addin to determine the index of the containing
slide, or, if this is impossible, the visibility state of the addin (i.e.
whether the containing slide is currently visible on screen).
The documentation suggests
no API specifically intended for this purpose, so I've been using
the following method:
Upon addin initialization (inside Document.initialize callback),
request currently selected slide using Document.getSelectedDataAsync
method.
Since addin cannot be initialized until it is visible, we can be almost
sure that the index obtained in the step 1 is the one of the containing slide
(unless the user was fast enough to change the slide while
getSelectedDataAsync was doing its async communication).
However, the assumption made in the step 2 has proved to be wrong. It holds
for PowerPoint Online, but desktop PowerPoint behaves differently.
Specifically, in slide show mode, if the slide next to the currently displayed one
contains an addin, and that addin is not yet initialized, it gets pre-initialized
despite the fact that it is not visible/active. And in all such pre-initialized
addins, Document.getSelectedDataAsync returns the index of the slide that is currently
displayed, which is not the one that contains the addin.
So the question is: is there a way to more or less reliably determine the containing
slide index, the way that works in both web and desktop versions of PowerPoint?
If no, here's the second question: is there a way for an addin to determine whether the containing slide is currently visible on screen in slide show mode?
I've found one that works in PowerPoint Online (checking window.innerHeight in
slide show mode), but it relies on internal implementation details that are
subject to change any time, and, most critically, it doesn't work in desktop
PowerPoint.
Desktop PowerPoint seems to display each addin in a separate window (as
window.parent equals window), and I failed to find an API or workaround that
would allow to tell whether the window is currently visible.
Page Visibility API
seems to fit this purpose perfectly, and it is even implemented in IE11, but
it doesn't work inside PowerPoint (visibilitychange events don't fire,
document.visibilityState always equal "visible", even if the addin is
on a currently hidden slide).
At present, the PowerPoint client seems return the active slide instead of the parent slide since the function “getSelectedDataAsync” is asynchronous.
is there a way to more or less reliably determine the containing slide index, the way that works in both web and desktop versions of PowerPoint?
As far as I know, there is no API to return the slide which contains the content app. And if you want the Office add-in support this API, you can submit the feedback from here.
While editing a PowerPoint document, I select a slide with bullet points then click Slide Show - Animation Schemes. I select the Appear and dim scheme, but the selection doesn't "stick" - the active animation scheme still shows as "No Animation".
I've verified that the "Show Without Animation" option is NOT checked. What else would cause this behavior?
As it turns out, the PowerPoint presentation file I was working on, which had been passed on to me from someone else, was originally set up using a template from a later version of PowerPoint. Apparently, that version had settings that were not accessible in PowerPoint 2003, so it just didn't work.
Fortunately, we'll be joining the modern world of MS Office soon and won't be dealing with this kind of problem.