oObject.Methods.method1 par1, par2 ...
Calling the methods for WEB is protected by the WebMethods permission.
Calling this method for Web pictures should be used with limit because each such calling performs a XML communication with the server! If, for example, 100 items were in the picture and this method in the onRefresh event was called in each such item, then 100 communications would been performed step by step during each refresh of the picture, which wouldn't been probably acceptable.
The PmSequencer object is special because its main event onStep can be executed in both main or working thread ("thread:work;" or "thread:main;"). Therefore the methods were doubled internally and then compiled in both main and working thread. If the method is called from the working thread then it is executed in this thread. In other cases it is executed in the main theread (as other object methods are).
This allows easy creation of auxiliary functions making the onStep event itself much better arranged. Even if the onStep is called alternatively in main and working thread the method is then called in the corresponding thread.
oObject.Methods.Init x, y
bResult = oObject.Methods.Close()