MuPDF 1.22.0 Documentation
document in one thread, and then sits there as a ‘server’ requesting pages and rendering them for other threads that need them, then the library is only ever being called from this one thread. Other threads time it is simplest to just use a different context for every thread; just create a new context at the same time as you create the thread. For more details see “Cloning the context” below. 2. “No simultaneous simultaneous calls to MuPDF in different threads are allowed to use the same document.” Only one thread can be accessing a document at a time, but once display lists are created from that document, multiple0 码力 | 175 页 | 698.87 KB | 7 月前3MuPDF 1.23.0 Documentation
document in one thread, and then sits there as a ‘server’ requesting pages and rendering them for other threads that need them, then the library is only ever being called from this one thread. Other threads time it is simplest to just use a different context for every thread; just create a new context at the same time as you create the thread. For more details see “Cloning the context” below. 2. “No simultaneous simultaneous calls to MuPDF in different threads are allowed to use the same document.” Only one thread can be accessing a document at a time, but once display lists are created from that document, multiple0 码力 | 245 页 | 817.74 KB | 7 月前3MuPDF 1.25.0 Documentation
document in one thread, and then sits there as a ‘server’ requesting pages and rendering them for other threads that need them, then the library is only ever being called from this one thread. Other threads time it is simplest to just use a different context for every thread; just create a new context at the same time as you create the thread. For more details see “Cloning the context” below. 2. “No simultaneous simultaneous calls to MuPDF in different threads are allowed to use the same document.” Only one thread can be accessing a document at a time, but once display lists are created from that document, multiple0 码力 | 259 页 | 1.11 MB | 7 月前3MuPDF 1.24.0 Documentation
document in one thread, and then sits there as a ‘server’ requesting pages and rendering them for other threads that need them, then the library is only ever being called from this one thread. Other threads time it is simplest to just use a different context for every thread; just create a new context at the same time as you create the thread. For more details see “Cloning the context” below. 2. “No simultaneous simultaneous calls to MuPDF in different threads are allowed to use the same document.” Only one thread can be accessing a document at a time, but once display lists are created from that document, multiple0 码力 | 249 页 | 830.15 KB | 7 月前3PyMuPDF 1.24.2 Documentation
CHAPTER SIXTEEN MULTIPROCESSING MuPDF has no integrated support for threading - calling itself “thread-agnostic”. While there do exist tricky possibil- ities to still use threading with MuPDF, the baseline threading support. Using in a Python threading environment will lead to blocking effects for the main thread. However, there is the option to use Python’s multiprocessing module in a variety of ways. If you caching-mechanism to reduce parsing of a page 2. as a data structure in multi-threading setups, where one thread parses the page and another one renders pages. This aspect is currently not supported by PyMuPDF0 码力 | 565 页 | 6.84 MB | 1 年前3PyMuPDF 1.12.2 documentation
caching-mechanism to reduce parsing of a page 2. as a data structure in multi-threading setups, where one thread parses the page and another one renders pages. This aspect is currently not supported by PyMuPDF0 码力 | 387 页 | 2.70 MB | 1 年前3
共 6 条
- 1