36 |
37 |
38 |
39 |
40 |
41 |
The Start Task onClick handler is defined as
42 |
43 | $(#start-task).onClick = function()
44 | {
45 | var taskElem = $(div#tasks > select)
46 | .$append(<option>Task { ++taskNo }
47 | <progress max=100 />
48 | <span.result /></option>);
49 | function onProgress(p100) {
50 | taskElem.$(progress).value = p100;
51 | }
52 | function onDone(taskId) {
53 | taskElem.$(span.result).text = "Done!";
54 | taskElem.$(progress).remove();
55 | }
56 | view.exec_task(taskId, onProgress, onDone);
57 | }
58 |
59 |
60 |
It defines couple of callback functions and calls view.exec_task() with them.
61 |
The view.exec_task() native method is implemented in EventHandler::exec_task().
62 |
The EventHandler::exec_task() starts worker thread passing taskNo, onProgress and
63 | onDone parameters to it.
64 |
Worker thread body is defined in Rust code as:
65 |
66 | // worker thread body, simulate time consuming task
67 | fn thread_body(task_no: i32, progress: Value, done: Value)
68 | {
69 | for i in 1..100 {
70 | std::thread::sleep(std::time::Duration::from_millis(100));
71 | progress.call(None, &make_args!(i), None).unwrap(); // report task progress
72 | }
73 | // report task completion,
74 | // we can pass some result data here, for now just taskId
75 | done.call(None, &make_args!(task_no), None).unwrap();
76 | }
77 |
78 |
As you see it calls passed callback functions.
79 |
80 |