Clarify arguments sent via ipc
This commit is contained in:
parent
03dd94d2b2
commit
2c6e5d0464
2 changed files with 2 additions and 2 deletions
|
@ -52,7 +52,7 @@ The `ipcRenderer` module has the following methods for sending messages:
|
|||
* `arg` (optional)
|
||||
|
||||
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`.
|
||||
|
||||
### `ipcRenderer.sendSync(channel[, arg1][, arg2][, ...])`
|
||||
|
|
|
@ -693,7 +693,7 @@ Opens the developer tools for the service worker context.
|
|||
* `arg` (optional)
|
||||
|
||||
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.
|
||||
|
||||
An example of sending messages from the main process to the renderer process:
|
||||
|
|
Loading…
Add table
Reference in a new issue