Здравствуйте еще раз. Если кто посмотрел скрипт в топике mdm форума (см. выше), возможно задался вопросом: что за константа ASYNC такая? В доках о ней вроде я ничего не видел (надо еще глянуть
). Неожиданно быстро получил ответ на том же форуме:
"mdm.ASYNC is a switch, it should does not matter what value it has, it imply a constant that could be provided as last argument (additional to required arguments in given method) - if provided ZINC tries to execute invoked method in async way - that is wrapper return immadiately letting next line of flahs code to execute, it is appliable only for methods that are type of Void - that is they do not return anything, using it for methods
that are expected to provide results (say like mdm.Database.MSAccess.getData()) does not make sense - because there
is no other way to get results from {mdm} script v.2 methods in async way (unless explicitely introduced by "events" methods for some objects - say like mdm.Browser.onDocumentComplete)"
B еще :
"Synchronous API Considerations (When changing to {mdm}script v2)
While {mdm}script 2.0 by default is synchronous, in some cases you might want to make the calling of a method asynchronous. This allows the flash player to continue its playback and scripting while the Zinc method is busy.
To make any {mdm}script 2.0 call asynchronous, you must add one more parameter to the end which defines it as such:
Synchronous call: mdm.Dialogs.prompt(“Hello”);
Asynchronous call: mdm.Dialogs.prompt(“Hello”,mdm.ASYNC);
NOTE: {mdm}script 1.0 calls are Asynchronous."
А здесь
http://www.mdmforum.com/forum/index....73&#entry81773 есть отличный пример использования с progressbar'ом. Без ASYNC привязать процесс к progressbar'у в цинке наверно не получится..