AutoSave not working in PowerPoint for pptm file - powerpoint

When I try to turn on AutoSave in PowerPoint (Microsoft 365 version) for a .pptm file, I get this message:
I assume this is because I'm using the pptm format, but I can't find any doc that says this is unsupported. In fact, this doc says it is.
You can also take steps as a developer to mitigate these problems so
that your add-ins and macros work smoothly, even if AutoSave is
enabled.
If AutoSave of a pptm file is unsupported, when did that happen and where is it documented?
Otherwise, any ideas on how I can get AutoSave working? I was going to use Office Add-ins instead of VBA until I found how severely limited the API is.

Related

Code Index API / Code Index Client Applications permissions requested in Visual Studio

A few months ago Visual Studio started popping up a permissions request for "Code Index Client Applications" from "Code Index API".
If I click on the "Report it here" link, I'm taken to another page that says it is from "AME.GBL".
I don't know what this is, so I always hit cancel. I have not noticed any kind of problems with not granting it what it wants, and I'm getting tired of it asking, so I'd like to try and remove whatever it is that is asking. I've tried disabling all my extensions, but it still asks. I have looked in the Visual Studio Installer's "Individual components" and also my Windows "Apps & features", but there is nothing with these names listed there. I have looked online but can't find anything about it.
Does anyone know what this is or how to get rid of it (or is there some reason why I should grant it permission)?
The dialog that pops up has changed slightly and I think it gives the answer:
You can read about Rich Code Navigation here or see a demo of it (primarily in Visual Studio Code) here. Note that the second link is from 2018, so in one form or another, this has been around for some time, but perhaps it has been off by default until a recent update?
At any rate, if you choose to disable Rich Code Navigation, you can do that under
Tools --> Options --> Environment --> Preview features
I did that and the permissions request dialog went away.

How can I save code changes in debugging mode in vb6

When an app stops in debugging mode and I make changes to the code
Is there a way to save the code with the changes, without stop the app?
Although the VB6 IDE does not provide this natively, an add-in for the IDE called MZTools has been around for ages which adds this feature.
Personally I've used MZTools 3.0 for many years, and this works really well.
This is what its help system says:
Shortcut To Save File At Debug-Time
The Shortcut To Save File At Debug-Time feature allows you to define a keyboard shortcut (Options
window, Shortcuts tab) to save the selected file at debug-time. The
Visual Basic IDE does not allow to save files at debug-time, but often
it is useful to save the modifications that you have made to the
source code at debug-time.
Remarks:
This feature is not available in the VBA version of MZ-Tools. This
feature only works at debug-time. Since Visual Basic disables buttons
or menus of add-ins at debug-time, the only way to save a file at
those times is through a keyboard shortcut. The file must be
previously saved at design-time, that is, MZ-Tools does not prompt for
a name to save the file (it shows an error message instead).
This is the options window for how I have it configured locally:
Note that originally MZTools was free in version 3 and later they switched to a paid version; if I hadn't gotten v3 originally however it would be well worth paying for, not only for this feature.
The short answer is you can't.
If you make the project before the crash, maybe this piece of code can be found in a ".tmp" file. But searching in .tmps is often a waste of time.
I particularly always force myself to stop the debug and save my progress.
And I always use this setting which forces me to remember to save:

Dynamics CRM 2015 not updating JavaScript file properly

The problem:
After editing my JavaScript file in the CRM textediting program, the changes are not updated when I test it in CRM. I am making subtle changes to a drop-down, nothing that breaks anything.
I am using Firefox, and unable to test this in other browsers (at least for the time being).
What I did was:
Made subtle changes to my javaScript file in the texteditor in MS Dynamics CRM 2015.
Press Publish all adjustments.
Open a new window with CRM.
Go to a formula with the drop-down, open it and find that it has not been updated.
So I open the debugger (F12) and confirm this.
In the debugger I open the tool setting and check the box with "Deactivate cache (when tool is open)".
Hit F5 test again and it works! VOILA!
However if I shut the whole thing down (the browser) and open it up again, then CRM still loads the old JavaScript file, until I go to the debugger and do the whole thing again.
This is not acceptable, since CRM are suppose to load the updated JavaScript file as default.
Any help or advice is appreciated.
Thank you.
The answer to this question is: Remember to clear the cache.
One good way to test it, is by opening a browser with private browsing.

Detect file changes outside the Visual Basic 6 IDE?

Background
I am working with VB6 legacy code and I am using an external editor because of the features that it has. Unfortunately, those changes aren't refreshed in the IDE because VB6 doesn't monitor loaded code for changes.
I have done some extensive searching on the subject including looking for alternative editors, a fairly exhaustive internet search including following all of the links on this StackExchange link and haven't found a way to refresh the code window to reflect the external file changes.
My company doesn't have access to the latest edition of Visual Studio and will not be purchasing it anytime in the near future. Until then, there is code to fix.
Question
Aside from restarting the program are there any methods that can be used to refresh the code displayed in the VB6 editing window?
Check out vbAdvance add on. It will prompt you to reload source file in case of external modification.
I think a found one possible solution.
The MZ-Tools set has an function called Reload file from Disk. It also allowed me to create a shortcut for this function through the MZ-Tools options menu, so I assigned it to the shortcut keys of my choosing.
It's a solution, but I'm still looking for anything that might be better.

debugging firefox extensions

I'm building an extension for Firefox.
I've checked the javascripts and they work well.
I've tried to make all the modules of the extensions right. But every time I try to install the plug-in into my firefox it says "Impossible to Install.. the component is damaged".
I'm looking for an "extension debugger" that can find the error that makes my add-on not working. Any advise?
I was looking for a link to Firefox background page debugging.
I found this link to Firefox debugging.
It says to follow these steps:
open Firefox
enter "about:debugging" in the URL bar
check the box labelled "Enable add-on debugging"
click the "Debug" button next to your extension
click "OK" in the warning dialog.
I don't think there is a dedicated debugger for that. Look at this article, maybe it can help: http://blogger.ziesemer.com/2007/10/javascript-debugging-in-firefox.html
Regards, Hiawatha
There are some debuggers for Firefox extensions, inparticular Venkman and Chromebug (which only works reliably with Firefox v5).
These will be able to break (pause code execution and launch debugger) when an exception occurs but don't usually help when you've got packaging problems, which are often caused by
Bad manifests - look though Mozilla's packaging documentation, in particular the format of manifests.
Errors in XML - validate all XML files (such as install.rdf).
Referenced files that are missing (e.g. a DTD referenced in the XML that is missing)
With the lack of tools, the best option is often to compare your extension's manifests and directory structure against a known good extension (e.g. an example Hello World extension, or an earlier version of your extension) as something as simple as a wrong entity in a DTD file can cause the error you are seeing.
Is this is a classic extension or the more recent bootstrapped type?
I would recommend to check the text encoding of install.rdf, chrome.manifest and bootstrap.js. Anything else than ANSI would be a cause of troubles.

Resources