Просмотр исходного кода

Fixed another problem with process enactment in documentation

Yentl Van Tendeloo 7 лет назад
Родитель
Сommit
282797d2ef
1 измененных файлов с 1 добавлено и 1 удалено
  1. 1 1
      doc/process_enactment.rst

+ 1 - 1
doc/process_enactment.rst

@@ -40,7 +40,7 @@ The call then becomes::
     ...     instantiate(None, "P2T", (p, t))
     ...     # Alternatively, we could have used raw_input() or so to prompt the user
     ...
-    >>> process_execute("models/query_state_space", "my_", {"models/refine_petrinet": callback})
+    >>> process_execute("models/query_state_space", {}, {"models/refine_petrinet": callback})
 
 When the process executes *refine_petrinet*, the callback function is executed, and the manual operation is terminated when the function terminates.
 Other types of operation, such as *model transformations* and *action language* can also have a callback function, but this is usually less important to end users and is therefore not elaborated on here.