Common questions about WPS Macro Editor usually involve the default development environment, macro-enabled file formats, and cross-platform compatibility; this FAQ includes 4 frequent questions and a glossary.
FAQ
Why does WPS open the VBA editor instead of the JS macro editor?
- Click File and open Options.
- Open the View tab.
- Select Default JS Development Environment and save the setting.
- Return to the developer tools area and check whether the JS macro editor now opens first.
Why can’t my macro code be saved?
- Check the current file format of the document.
- If the file is
.docx, change it to a macro-enabled format. - In WPS Writer, save the file as
.docmor another format that retains macro code. - Reopen the file and confirm that the macro content is still present.
Why can’t VBA macros written on Windows run directly on Linux or Mac?
- Confirm whether the current macro uses VBA or JS.
- Review the differences in macro environments and scripting languages across systems.
- If you need to continue on Linux or Mac, rebuild the logic with JS macros.
- Test the script again on the target system.
What security points should I keep in mind when using the macro editor?
- Open only trusted macro scripts or macro-enabled documents.
- Confirm the purpose and content before running a script.
- Avoid running macro files from unknown sources.
- Keep a backup of important documents before testing macros.
Glossary
| Term | Definition |
|---|---|
| JS macro | An automation script written in JavaScript that can be created and maintained in WPS Macro Editor. |
| Default JS development environment | An option in WPS settings that makes the developer entry open the JS-related environment first. |
| Macro-enabled format | A file format that can retain macro code, such as .docm; standard .docx files do not retain macros. |
| VBA editor | A development environment for VBA macros, separate from the JS macro editor. |