SOLIDWORKS Bridge

' adom-hello.swp — PLACEHOLDER, not a runnable SOLIDWORKS macro yet.
'
' WHAT THIS FILE IS FOR
' swx_run_macro calls ISldWorks::RunMacro2(path, module, procedure, ...) and a
' caller needs something to point it at. This is the intended home of the
' bridge's own smallest working macro — the "does the macro road work at all"
' probe, run once against a live machine before anything relies on it.
'
' WHY IT IS A PLACEHOLDER AND NOT A MACRO
' A .swp IS plain text and IS editable by hand (CodeStack documents this, and it
' is why shipping a text file here is possible at all), but this bridge has not
' yet run a macro against a live SOLIDWORKS. Shipping a file that LOOKS like a
' working macro, in a repository whose whole discipline is separating "proven
' live" from "written from documentation", would be the one kind of dishonesty
' that matters here: the next person would assume it had been run. It has not.
' The real template gets recorded from SOLIDWORKS' own macro recorder — which is
' the only way to be sure of the module and procedure names it expects — and
' replaces this file wholesale.
'
' THE SHAPE IT WILL HAVE (module `main`, procedure `main` — the recorder's
' defaults, and swx_run_macro's defaults for that reason):
'
'   Dim swApp As SldWorks.SldWorks
'   Sub main()
'       Set swApp = Application.SldWorks
'       swApp.SendMsgToUser2 "adom bridge: hello", 1, 1
'   End Sub
'
' Even that is a guess about SendMsgToUser2 raising a modal — which this bridge
' must never do on somebody's desktop — so the recorded template will almost
' certainly write to a file or set a custom property instead. Recorded first,
' shipped second.