Suggestion
It would be great if all the AutomationId properties of all AutomationElements could be available to Windows.Automation.
Why?
Someone might ask, what is it or why? AutomationId's make it possible to Automate anything in the Logos User Interface without any trouble. I wrote my own system in powershell and would like to distribute it free to the FaithLife community. The only drawback is the uncertainty and lack of AutomationId's. I used some workarounds to accomplish some automation tasks. This could unleash the full automation potential of the software. Without to much Technical Info, here are some screenshots.
What can be done?
Some tasks could be done with the ComAPI. But automation boosts creativity. If you can do it in Logos it can be done via Automation. You can create macro's to automate almost anything you like to do frequently. And the best of all, it's in a language anyone can understand. Most users don't realise the need or potential available until they discover how easy everything could actually be.
Please, please, please impliment all AutomationId's
