Use point / size / rectangle structures consistently in API docs

This commit is contained in:
Milan Burda 2017-04-04 00:35:39 +02:00
parent 7265a0c1b4
commit 568454525d
9 changed files with 25 additions and 50 deletions

View file

@ -6,13 +6,9 @@
* `scaleFactor` Number - Output device's pixel scale factor.
* `touchSupport` String - Can be `available`, `unavailable`, `unknown`.
* `bounds` [Rectangle](rectangle.md)
* `size` Object
* `height` Number
* `width` Number
* `size` [Size](size.md)
* `workArea` [Rectangle](rectangle.md)
* `workAreaSize` Object
* `height` Number
* `width` Number
* `workAreaSize` [Size](size.md)
The `Display` object represents a physical display connected to the system. A
fake `Display` may exist on a headless system, or a `Display` may correspond to

View file

@ -0,0 +1,4 @@
# Point Object
* `x` Number
* `y` Number

View file

@ -0,0 +1,4 @@
# Size Object
* `width` Number
* `height` Number