electron/docs/api/ipc-renderer.md

79 lines
2.5 KiB
Markdown
Raw Normal View History

2015-11-10 08:48:24 +00:00
# ipcRenderer
2013-08-14 22:43:35 +00:00
The `ipcRenderer` module is an instance of the
[EventEmitter](https://nodejs.org/api/events.html) class. It provides a few
methods so you can send synchronous and asynchronous messages from the render
process (web page) to the main process. You can also receive replies from the
main process.
2015-08-27 00:56:10 +00:00
2015-11-10 08:48:24 +00:00
See [ipcMain](ipc-main.md) for code examples.
2013-08-14 22:43:35 +00:00
2015-11-10 08:48:24 +00:00
## Listening for Messages
2015-08-27 00:56:10 +00:00
2015-11-10 08:48:24 +00:00
The `ipcRenderer` module has the following method to listen for events:
2015-08-27 00:56:10 +00:00
2015-11-10 08:48:24 +00:00
### `ipcRenderer.on(channel, callback)`
2015-08-27 00:56:10 +00:00
2015-11-10 08:48:24 +00:00
* `channel` String - The event name.
* `callback` Function
When the event occurs the `callback` is called with an `event` object and
arbitrary arguments.
### `ipcRenderer.removeListener(channel, callback)`
* `channel` String - The event name.
* `callback` Function - The reference to the same function that you used for
`ipcRenderer.on(channel, callback)`
Once done listening for messages, if you no longer want to activate this
callback and for whatever reason can't merely stop sending messages on the
channel, this function will remove the callback handler for the specified
channel.
### `ipcRenderer.removeAllListeners(channel)`
* `channel` String - The event name.
This removes *all* handlers to this ipc channel.
2016-02-03 20:15:13 +00:00
### `ipcRenderer.once(channel, callback)`
2016-02-03 20:15:13 +00:00
Use this in place of `ipcRenderer.on()` to fire handlers meant to occur only once,
as in, they won't be activated after one call of `callback`
2015-11-10 08:48:24 +00:00
## Sending Messages
The `ipcRenderer` module has the following methods for sending messages:
2015-08-27 00:56:10 +00:00
2015-11-10 08:48:24 +00:00
### `ipcRenderer.send(channel[, arg1][, arg2][, ...])`
2015-08-27 00:56:10 +00:00
* `channel` String - The event name.
2015-08-28 21:57:14 +00:00
* `arg` (optional)
2015-08-27 00:56:10 +00:00
2015-11-10 08:48:24 +00:00
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
`channel` event with `ipcMain`.
2013-08-14 22:43:35 +00:00
2015-11-10 08:48:24 +00:00
### `ipcRenderer.sendSync(channel[, arg1][, arg2][, ...])`
2013-08-14 22:43:35 +00:00
2015-08-27 00:56:10 +00:00
* `channel` String - The event name.
2015-08-28 21:57:14 +00:00
* `arg` (optional)
2013-08-14 22:43:35 +00:00
2015-11-10 08:48:24 +00:00
Send an event to the main process synchronously via a `channel`, you can also
send arbitrary arguments.
2013-08-14 22:43:35 +00:00
The main process handles it by listening for the `channel` event with
`ipcMain` and replies by setting `event.returnValue`.
2013-08-14 22:43:35 +00:00
2015-11-10 08:48:24 +00:00
__Note:__ Sending a synchronous message will block the whole renderer process,
unless you know what you are doing you should never use it.
2014-12-17 19:09:11 +00:00
2015-11-10 08:48:24 +00:00
### `ipcRenderer.sendToHost(channel[, arg1][, arg2][, ...])`
2014-12-17 19:09:11 +00:00
2015-08-27 00:56:10 +00:00
* `channel` String - The event name.
2015-08-28 21:57:14 +00:00
* `arg` (optional)
2014-12-17 19:09:11 +00:00
2015-11-10 08:48:24 +00:00
Like `ipcRenderer.send` but the event will be sent to the `<webview>` element in
the host page instead of the main process.