09-02-22 02:11 PM
09-02-22 03:23 PM
10-02-22 04:52 PM
Hi James,
I got around this, and several other challenges with MS Edge, by building a "wrapper object." Specific to your question, when you start MS Edge with the "--force-renderer-accessibility" parameter, if the BP extension is not active, it will throw an exception. I use that exception to then direct the WO to turn turn the extension on.
I use the URL of whichever setting I am trying to address to go directly to the option. In this case, "edge://extensions/". I ended up having to use UIA definitions to access the checkboxes, but the state of the checkbox is read accurately and the combination of "focus" and "Global Mouse Click Center" are able to change the state of the checkbox.
I have not had a problem with the rest of the object picking up immediately after enabling the extension, but your experience may vary. It might be a better option to close out and restart MS Edge, if you wanted to be absolutely certain.
If any of this doesn't make sense, please let me know and I can try to clarify.
Good Luck,
Red
11-02-22 07:47 AM
Thanks for the suggestions.
I have already started to create a Win32 object that will then allow me to interreact with the settings of Edge and so far seems to be ok.
I have also been told that potentially removing and reinstalling the extension can help prevent it randomly turning itself off so I am going to try that option too.