Detalied documentation about frameBuffer's format.
This commit is contained in:
parent
44ee74a9b1
commit
8734395358
1 changed files with 5 additions and 2 deletions
|
@ -565,8 +565,11 @@ For the `mouseWheel` event, the `event` object also have following properties:
|
||||||
Begin subscribing for presentation events and captured frames, the `callback`
|
Begin subscribing for presentation events and captured frames, the `callback`
|
||||||
will be called with `callback(frameBuffer)` when there is a presentation event.
|
will be called with `callback(frameBuffer)` when there is a presentation event.
|
||||||
|
|
||||||
The `frameBuffer` is a `Buffer` that contains raw pixel data, in the format of
|
The `frameBuffer` is a `Buffer` that contains raw pixel data. On most machines,
|
||||||
32bit ARGB.
|
the pixel data is effectively stored in 32bit BGRA format, but the actual
|
||||||
|
representation depends on the endianness of the processor (most modern
|
||||||
|
processors are little-endian, on machines with big-endian processors the data
|
||||||
|
is in 32bit ARGB format).
|
||||||
|
|
||||||
### `webContents.endFrameSubscription()`
|
### `webContents.endFrameSubscription()`
|
||||||
|
|
||||||
|
|
Loading…
Add table
Add a link
Reference in a new issue