3D Graphics for Dummies3D Graphics for Dummies Significant content “borrowed” from Dan Chang @ Nintendo NTD “with permission” Chris Ryan CppCon 2021 github.com/ChrisR98008/CppCon20213 3D Graphics for Dummies4 3D Graphics Dummies5 3D Graphics for Dummies6 3D Graphics for Dummies7 3D Graphics for Dummies8 3D Graphics for Dummies9 3D Graphics for Dummies10 3D Graphics for Dummies11 3D Graphics for Dummies12 3D Graphics Graphics for Dummies13 3D Graphics for Dummies14 3D Graphics for Dummies15 3D Graphics for Dummies Winding / Right Hand Rule Fingers curled in the order of the points, thumb points up Counter clockwise0 码力 | 79 页 | 4.61 MB | 6 月前3
 MuPDF 1.22.0 Documentation&pix->samples[y * pix->stride]; for (x = 0; x < pix->w; ++x) { if (x > 0) printf(" "); printf("%3d %3d %3d", p[0], p[1], p[2]); p += pix->n; } printf("\n"); } (continues on next page) 2.1. Basic MuPDF place to prevent the calls being simultaneous. 4. “An fz_locks_context must be supplied at context creation time, unless MuPDF is to be used purely in a single thread at a time.” MuPDF needs to protect against undefined if none exists. size The size in bytes of the embedded file contents. creationDate The creation date of the embedded file. modificationDate The modification date of the embedded file. 3.4.0 码力 | 175 页 | 698.87 KB | 8 月前3
 MuPDF 1.25.0 Documentation&pix->samples[y * pix->stride]; for (x = 0; x < pix->w; ++x) { if (x > 0) printf(" "); printf("%3d %3d %3d", p[0], p[1], p[2]); p += pix->n; } (continues on next page) 2.1. Basic MuPDF usage example place to prevent the calls being simultaneous. 4. “An fz_locks_context must be supplied at context creation time, unless MuPDF is to be used purely in a single thread at a time.” MuPDF needs to protect against undefined if none exists. size The size in bytes of the embedded file contents. creationDate The creation date of the embedded file. modificationDate The modification date of the embedded file. 7.4.40 码力 | 259 页 | 1.11 MB | 8 月前3
 MuPDF 1.23.0 Documentation&pix->samples[y * pix->stride]; for (x = 0; x < pix->w; ++x) { if (x > 0) printf(" "); printf("%3d %3d %3d", p[0], p[1], p[2]); p += pix->n; } printf("\n"); } (continues on next page) 2.1. Basic MuPDF place to prevent the calls being simultaneous. 4. “An fz_locks_context must be supplied at context creation time, unless MuPDF is to be used purely in a single thread at a time.” MuPDF needs to protect against undefined if none exists. size The size in bytes of the embedded file contents. creationDate The creation date of the embedded file. modificationDate The modification date of the embedded file. 6.4.40 码力 | 245 页 | 817.74 KB | 8 月前3
 Nim 2.0.8 Manualthe same pragmas are available as for ordinary variables. As let statements are immutable after creation they need to de�ne a value when they are declared. The only exception to this is if the {.importc context at instantiation are considered: In the example, the generic `==` for tuples (system.html#%3D%3D%2CT%2CT_2) (as de�ned in the system module) uses the == operators of the tuple's components. However lib/pure/strutils.toUpperAscii("abc") import lib/pure/strutils as strutils import "gfx/3d/somemodule" # in quotes because '3d' is not a valid Nim identifier From import statement After the from keyword, a0 码力 | 132 页 | 5.73 MB | 1 年前3
 MuPDF 1.24.0 Documentation&pix->samples[y * pix->stride]; for (x = 0; x < pix->w; ++x) { if (x > 0) printf(" "); printf("%3d %3d %3d", p[0], p[1], p[2]); p += pix->n; } (continues on next page) 2.1. Basic MuPDF usage example place to prevent the calls being simultaneous. 4. “An fz_locks_context must be supplied at context creation time, unless MuPDF is to be used purely in a single thread at a time.” MuPDF needs to protect against undefined if none exists. size The size in bytes of the embedded file contents. creationDate The creation date of the embedded file. modificationDate The modification date of the embedded file. 6.4.40 码力 | 249 页 | 830.15 KB | 8 月前3
 Hyperledger Fabric 1.2 Documentationordering service, and the channel configuration transaction file is broadcast to the orderer at Channel creation time. The anchor peer transactions, as the name might suggest, specify each Org’s Anchor Peer on the peer’s MSP to instantiate chaincode. Package signing A chaincode package that was signed at creation can be handed over to other owners for inspection and signing. The workflow supports out-of-band Signed- CDS and must also be a writer on the channel, which is configured as part of the channel creation. This is important for the security of the channel to prevent rogue entities from deploying chaincodes0 码力 | 335 页 | 4.48 MB | 1 年前3
 Hyperledger Fabric 1.2 Documentationordering service, and the channel configuration transaction file is broadcast to the orderer at Channel creation time. The anchor peer transactions, as the name might suggest, specify each Org’s Anchor Peer on the peer’s MSP to instantiate chaincode. Package signing A chaincode package that was signed at creation can be handed over to other owners for inspection and signing. The workflow supports out-of-band in SignedCDS and must also be a writer on the channel, which is configured as part of the channel creation. This is important for the security of the channel to prevent rogue entities from deploying chaincodes0 码力 | 497 页 | 6.59 MB | 1 年前3
 Hyperledger Fabric 1.3 Documentationorganization R1 to administer the network. R4 did this by adding R1 to the policies for channel creation and consortium creation. Because of this change, R1 was able to define the consortia X1 and X2, and create the ordering service, and the channel configuration transaction file is broadcast to the orderer at Channel creation time. The anchor peer transactions, as the name might suggest, specify each Org’s Anchor Peer on the peer’s MSP to instantiate chaincode. Package signing A chaincode package that was signed at creation can be handed over to other owners for inspection and signing. The workflow supports out-of-band0 码力 | 528 页 | 6.85 MB | 1 年前3
 Hyperledger Fabric 1.3 Documentationorganization R1 to administer the network. R4 did this by adding R1 to the policies for channel creation and consortium creation. Because of this change, R1 was able to define the consortia X1 and X2, and create the ordering service, and the channel configuration transaction file is broadcast to the orderer at Channel creation time. The anchor peer transactions, as the name might suggest, specify each Org’s Anchor Peer on the peer’s MSP to instantiate chaincode. Package signing A chaincode package that was signed at creation can be handed over to other owners for inspection and signing. The workflow supports out-of-band0 码力 | 367 页 | 4.95 MB | 1 年前3
共 1000 条
- 1
 - 2
 - 3
 - 4
 - 5
 - 6
 - 100
 













