native
Here are 1,821 public repositories matching this topic...
-
Updated
Jan 7, 2022 - Objective-C
-
Updated
Oct 31, 2021 - JavaScript
-
Updated
Sep 2, 2021 - TypeScript
-
Updated
Dec 31, 2021 - TypeScript
-
Updated
Jun 10, 2020 - Java
-
Updated
Jan 4, 2022 - JavaScript
-
Updated
Jan 7, 2022 - Red
We should add a compile-time check when trying to use extern in an unsupported manner.
For example extern cannot be used in val foo: Int = extern
Also, it should report usages as a default parameter of methods, if it is not runtime exceptions should contain information about unsupported usage of the extern method.
No version of 'react-native-dom' found that satisfies a peer dependency on 'react-native@0.56.0'
When use "$: react-native dom"
Appears:
No version of 'react-native-dom' found that satisfies a peer dependency on 'react-native@0.56.0'
This is my package.json:
{
"name": "dom",
"version": "0.0.1",
"private": true,
"scripts": {
"start": "node node_modules/react-native/local-cli/cli.js start",
"test": "jest"
},
"dependencies": {
"react": "16.4.1",
"
-
Updated
Jan 4, 2022 - Objective-C
-
Updated
Jan 7, 2022 - D
-
Updated
Jan 7, 2022 - Java
-
Updated
Jul 9, 2021 - TypeScript
-
Updated
Dec 26, 2021 - Swift
-
Updated
May 9, 2021 - JavaScript
Summary of feature
Silk.NET.DXGI is doesn't have the constant/flag DXGI_CREATE_FACTORY_DEBUG.
Comments
I have to type by hand the 0x1 which is the value of DXGI_CREATE_FACTORY_DEBUG, it would be nice to be able to just grab it from the DXGI class, like DXGI.CpuAccessNone.
This is useful to make it easier to pass the correct value to DXGI.GetApi().CreateDXGIFactory2
https://docs.micr
-
Updated
Jan 26, 2018 - Pascal
-
Updated
Jan 7, 2022 - Java
-
Updated
Dec 27, 2021 - C
-
Updated
Jan 4, 2022 - Pascal
Improve this page
Add a description, image, and links to the native topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the native topic, visit your repo's landing page and select "manage topics."


Since we also expose the Skia-bindings for a Canvas-like API I think it might be a good idea to start refactoring the API to utilise more named arguments e.g.
~x=..., ~y=....What do you others think?