RGB pixmap. */ fz_try(ctx) pix = fz_new_pixmap_from_page_number(ctx, doc, page_number, ctm, fz_ ˓→device_rgb(ctx), 0); fz_catch(ctx) { fprintf(stderr, "cannot render page: %s\n", fz_caught_message(ctx)); different threads are allowed to use the same device.” Calling a device simultaneously from different threads will cause it to get confused and may crash. Calling a device from several different threads is perfectly 2.4. Multi-threading 13 MuPDF Documentation, Release 1.21.2 (continued from previous page) fz_device *dev = NULL; fprintf(stderr, "thread at page %d loading!\n", pagenumber); // The context pointer

DisplayListDevice . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114 6.16 Device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . RGB pixmap. */ fz_try(ctx) pix = fz_new_pixmap_from_page_number(ctx, doc, page_number, ctm, fz_ ˓→device_rgb(ctx), 0); fz_catch(ctx) { fprintf(stderr, "cannot render page: %s\n", fz_caught_message(ctx)); different threads are allowed to use the same device.” Calling a device simultaneously from different threads will cause it to get confused and may crash. Calling a device from several different threads is perfectly

DisplayListDevice . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119 7.16 Device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . RGB pixmap. */ fz_try(ctx) pix = fz_new_pixmap_from_page_number(ctx, doc, page_number, ctm, fz_ ˓→device_rgb(ctx), 0); fz_catch(ctx) { fz_report_error(ctx); fprintf(stderr, "cannot render page\n"); fz_drop_document(ctx different threads are allowed to use the same device.” Calling a device simultaneously from different threads will cause it to get confused and may crash. Calling a device from several different threads is perfectly

DisplayListDevice . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114 6.16 Device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . RGB pixmap. */ fz_try(ctx) pix = fz_new_pixmap_from_page_number(ctx, doc, page_number, ctm, fz_ ˓→device_rgb(ctx), 0); fz_catch(ctx) { fz_report_error(ctx); fprintf(stderr, "cannot render page\n"); fz_drop_document(ctx different threads are allowed to use the same device.” Calling a device simultaneously from different threads will cause it to get confused and may crash. Calling a device from several different threads is perfectly

programs demo.py and demo-lowlevel.py. Among other things they contain details on how the TextPage, Device and DisplayList classes can be used for a more direct control, e.g. when performance considerations rectangles into which the story will be laid out, and the positioned text can then be drawn to an output device. This keeps the concept of the text itself (the story) to be separated from the areas into which more: # loop outputting the story device = writer.begin_page(MEDIABOX) # make new page more, _ = story.place(WHERE) # layout into allowed rectangle story.draw(device) # write on page writer.end_page()

General Remarks Unary Operations Binary Operations Low Level Functions and Classes Functions Device DisplayList TextPage Structure of TextPage.extractJSON() Full Document Output in JSON Format TextPage and at demo program demo.py. Among other things they contain details on how the TextPage, Device and DisplayList classes can be used for a more direct control, e.g. when performance considerations classes for the experienced user. To be used for special needs or performance requirements. Functions Device DisplayList TextPage Working together: DisplayList and TextPage © Copyright 2015-2018, Jorj X