Reflection Desktop v16 Run Macro Window

I support users of Assistive Technology software like the screen reader JAWS and I'm having some trouble consistently invoking a Reflection macro due to the weird behavior of the Run Macro window.  Since I know the name of the macro, is there a way to run the macro by bypassing the Run Macro window?

WRQDesciple,

You can assign a macro to a Menu item or a button in the interface.  Have a look at the following training videos for reference to adding a menu item (and include quick keys to get to that item) or a button to the ribbon or toolbar interface:

#HowTo Record a Macro When Using the Reflection Desktop Ribbon

#HowTo Customize Menus and Toolbars in Reflection Desktop Classic Mode

You can also access the online help for more information on customizing the ribbon.

You can also create custom keyboard maps that will allow you to assign macros to specific key combinations.

Best Regards,

Jeff

Thank you for your prompt response!  Especially on the eve of a holiday!

Unfortunately, neither assigning the macro to a button or menu item will work because the code module I need to run is in the ProjectLegacy folder of the project and not in the Common folder.  This is necessary because the display adjustment properties I need to change cannot be accessed by a code module in the Common folder.  When I try to make a new toolbar button or add a menu item, the only macro folder that comes up is the Common folder as if this function does not know about the other Project and ProjectLegacy folders.

Unless there's some naming convention that allows me to access ProjectLegacy properties from the Common folder?

Whatever choice you make to launch the macro manually through the interface pictured below:

should have a matching command for a button or menu option either the workspace macro on the left of the menu item below or one of the legacy choices on the right of the menu item below:

The item on the right I have highlighted "Run Embedded Legacy Reflection Macro" should access the "Projectlegacy" portion of the VBA file for your session.

Thanks,

Jeff