Files
2026-09-04 10:43:46 -07:00

2.3 KiB

Discovered APIs (from public manuals/tutorials only)

This document lists Multi-PROG Local Script host API names mentioned in the publicly linked manuals and tutorials cataloged in 02_Resource_Catalog/links.md. Names are unverified — no third-party scripts were decompiled or scraped to produce this list. Always confirm exact signatures, parameters, and behavior in your installed Multi-PROG Local Script > Help before writing real host-facing code.

Editor / lifecycle

  • AddFunctionButton(label, callback) — registers a button in the script's function panel (name as referenced in community tutorials; confirm exact casing/signature locally).
  • Local Script editor supports import, test, correct, and lock/publish workflow steps (per the official manual and blog walkthrough).
  • "Released Features" — the manual's term for the published/available function set exposed to the script.

Data I/O

  • ReadData(...) — reads bytes from the currently loaded buffer/device (name referenced in manual mirror; confirm arguments).
  • WriteData(...) — writes bytes to the currently loaded buffer/device (name referenced in manual mirror; confirm arguments and safety prompts).
  • File dialogs for opening/saving working copies are referenced in the manual mirror.

Conversion / comparison helpers

  • Hex2Dec(...) — hex-to-decimal conversion helper referenced in community material.
  • areEqual(...) — buffer/array equality helper referenced in community material.

Checksum / crypto references in the manual

  • The manual mirror lists sample entries referencing AES, DES, and SHA-256 in the context of supported checksum/verification routines. No algorithm parameters, keys, or offsets are included here — see 09_Collected_JS/ for independent, generic reference implementations of common hash/checksum algorithms.
  • A visual "green C" indicator and a checksum/verification prompt appear during supported writes (per the checksum workflow guides).

How to verify before use

  1. Open Multi-PROG's Local Script editor and use Help to list the actual exposed API and exact signatures on your installed version.
  2. Cross-reference against the manual PDF and mirror linked in the resource catalog.
  3. Never assume an API name or behavior from a third-party blog/forum post without confirming it locally.