mirrors/electron
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages 1 Wiki Activity Actions 1

Merge pull request #4453 from lukeapage/patch-6

Browse source 
Docs - clarify ipc arguments
This commit is contained in:
Cheng Zhao 2016-02-16 11:08:35 +08:00
commit d035fc2816
2 changed files with 2 additions and 2 deletions
Download patch file Download diff file Expand all files Collapse all files

2
docs/api/ipc-renderer.md
View file

@ -52,7 +52,7 @@ The `ipcRenderer` module has the following methods for sending messages:
* `arg` (optional) * `arg` (optional)
Send an event to the main process asynchronously via a `channel`, you can also Send an event to the main process asynchronously via a `channel`, you can also
send arbitrary arguments. The main process handles it by listening for the send arbitrary arguments. Arguments will be serialized (json) and hence no functions or prototype chain will be included. The main process handles it by listening for the
`channel` event with `ipcMain`. `channel` event with `ipcMain`.
### `ipcRenderer.sendSync(channel[, arg1][, arg2][, ...])` ### `ipcRenderer.sendSync(channel[, arg1][, arg2][, ...])`

2
docs/api/web-contents.md
View file

@ -693,7 +693,7 @@ Opens the developer tools for the service worker context.
* `arg` (optional) * `arg` (optional)
Send an asynchronous message to renderer process via `channel`, you can also Send an asynchronous message to renderer process via `channel`, you can also
send arbitrary arguments. The renderer process can handle the message by send arbitrary arguments. Arguments will be serialized (json) and hence no functions or prototype chain will be included. The renderer process can handle the message by
listening to the `channel` event with the `ipcRenderer` module. listening to the `channel` event with the `ipcRenderer` module.
An example of sending messages from the main process to the renderer process: An example of sending messages from the main process to the renderer process: