diff --git a/indepth/features/initialize.md b/indepth/features/initialize.md index 7c211f66..a764d94b 100644 --- a/indepth/features/initialize.md +++ b/indepth/features/initialize.md @@ -9,45 +9,7 @@ description: Dynamic Web TWAIN SDK Documentation Initialization Page # Initialize -Initializing Dynamic Web TWAIN takes a few simple steps, as you can see in the ["Getting Started"]({{site.getstarted}}helloworld.html)chapter. The following guide will dive deeper into how Dynamic Web TWAIN is intialized once the page loads. - -## Usage Editions - -Dynamic Web TWAIN can operate in two modes: Desktop Service or WebAssembly. - -### Desktop Service Edition - -#### What is Desktop Service Edition - -Desktop Service Edition means Dynamic Web TWAIN operates through the [Dynamsoft Service]({{site.indepth}}deployment/service.html) which is a quiet, background system service that handles the communication between connected devices and the browser client as well as imaging processing, encoding, decoding, etc. - -When using Dynamic Web TWAIN on [desktop]({{site.getstarted}}platform.html#browsers-on-desktop-devices), the service mode is used by default (recommended), and the installation of the Dynamsoft Service is mandatory for this mode. - -#### Installation of the Dynamsoft Service - -[Guide on how to install the Dynamsoft Service]({{site.indepth}}deployment/service.html#dynamsoft-service-is-not-installed-dynamic-web-twain-is-not-installed) - -### WebAssembly Edition - -#### What is WebAssembly Edition - -WebAssembly (WASM) Edition means Dynamic Web TWAIN operates completely within the browser with the help of **Web Worker** and **WebAssembly**. It relieves users from manually installing anything. This relies on some advanced features that only modern [WASM browsers]({{site.getstarted}}platform.html#wasm-browsers) provide though. - -If a user decides to access the Dynamic Web TWAIN application via [a mobile browser]({{site.getstarted}}platform.html#browsers-on-mobile-devices) or they don't want to install anything on [desktop]({{site.getstarted}}platform.html#browsers-on-desktop-devices), they can choose the WASM mode. - -Read more on how to [expand your application to mobile platforms]({{site.indepth}}development/upgrade.html#expand-your-application-to-mobile-platforms). - -#### How to use WebAssembly Edition on desktop - -As mentioned previously, [desktop]({{site.getstarted}}platform.html#browsers-on-desktop-devices) users will by default go with Desktop Service Edition, while mobile and tablet users will default to WebAssembly Edition. However, if you would like desktop users to start in WebAssembly Edition and forego the need for a service, you can set [UseLocalService]({{site.info}}api/Dynamsoft_WebTwainEnv.html#uselocalservice) to `false` in the initialization code. - -### Comparison of the two modes - -A major difference between Desktop Service Edition and WebAssembly Edition is that the latter can not access local devices, which means that it is impossible to [use local scanners]({{site.indepth}}features/input.html#scan-from-a-local-scanner). - -Also, the performance and speed of WebAssembly Edition is not as good as Service Edition because it is not able to make use of as many resources. - -At Dynamsoft, we tried and are still trying to make these two modes to function as closely to each other as possible. +Initializing Dynamic Web TWAIN takes a few simple steps, as you can see in the [Getting Started]({{site.getstarted}}helloworld.html) chapter. The following guide will dive deeper into the process how Dynamic Web TWAIN is intialized once the web page loads. ## Loading the Core JS Files @@ -55,114 +17,47 @@ This is the first step of the initialization. ### Introduction to the core files -Inside the `Resources` directory that is included with the SDK installation, you will find the following two files which are the main JS files that define the configuration and operation of Dynamic Web TWAIN. +Inside the `Resources` directory that is included in the SDK installation folder, you can find the following two main JS files which define the configurations and operation of Dynamic Web TWAIN: -- `dynamsoft.webtwain.config.js` - `dynamsoft.webtwain.initiate.js` -Let's break down each file's purpose: - -- `dynamsoft.webtwain.initiate.js` - - This file is the **core** of the Dynamic Web TWAIN JavaScript Library. You're not supposed to change it without consulting the [Dynamsoft Support Team]({{site.about}}Getsupport.html). - + This file is the **core** of the Dynamic Web TWAIN JavaScript Library. You're not supposed to change it without consulting the [Dynamsoft Support Team]({{site.about}}Getsupport.html). - `dynamsoft.webtwain.config.js` - This file is used for basic configuration of Dynamic Web TWAIN. This is where you configure the product key, change the initial viewer size, and more. - -**Q: Does it matter which JavaScript file is referenced first** - -**A**: Generally, both `dynamsoft.webtwain.initiate.js` and `dynamsoft.webtwain.config.js` need to be referenced. In the former file, it detects whether the latter has been loaded; if not, it'll wait. Therefore, it doesn't matter which file comes first. - -**Q: Why do I see `dynamsoft.webtwain.min.js` and `dynamsoft.webtwain.min.mjs` instead of the 2 files above** - -**A**: The two files are present in the official [npm package `dwt`](https://github.com/dynamsoft-dwt/web-twain-package). For simplicity, in each of these files Dynamsoft has included all necessary JavaScript code which includes both files mentioned above plus `dynamsoft.webtwain.install.js` and all extra components (add-ons). The `.js` file is a simple combination of the code while the `.mjs` file is built as an ECMAScript 6 (ES6) Module that is used in applications based on Angular, React, and Vue etc. + This file is used for setting basic configurations of Dynamic Web TWAIN, e.g., configure the product key, change the initial viewer size, and more. -In a regular application, referencing `dynamsoft.webtwain.min.js` alone would be more than enough than referencing `dynamsoft.webtwain.config.js` and `dynamsoft.webtwain.initiate.js`. +If you are using the official [NPM package `dwt`](https://github.com/dynamsoft-dwt/web-twain-package), you will see `dynamsoft.webtwain.min.js` and `dynamsoft.webtwain.min.mjs` instead. For simplicity, in each of these files Dynamsoft has included all necessary JavaScript code which includes both files mentioned above plus `dynamsoft.webtwain.install.js` and all extra components (add-ons). The `dynamsoft.webtwain.min.js` file is a simple combination of the code while the `dynamsoft.webtwain.min.mjs` file is built as an ECMAScript 6 (ES6) Module that is used in applications based on Angular, React, and Vue etc. ## Loading Add-on JS files -Dynamic Web TWAIN offers a number of add-ons, including a barcode reader, a PDF rasterizer, two webcam utilizers and two OCR engines. The files for these components reside in the **addon** subfolder in the **Resources** directory. [Learn more about the resource files]({{site.faq}}what-are-the-resources-files.html). +Dynamic Web TWAIN offers a number of optional add-ons, including a barcode reader, a PDF rasterizer, two webcam utilizers and two OCR engines. The files for these components reside in the **addon** subfolder in the **Resources** directory. [Learn more about the resource files]({{site.faq}}what-are-the-resources-files.html). -You can reference the respective JavaScript file to include any of these add-on components. Once a JavaScript file is referenced, the member methods/properties of that component are made available in the [Dynamsoft Namespace](#the-dynamsoft-namespace) and can later be used by the `WebTwain` instances. +You can reference the respective JS file to include any of these add-on components. Once a JS file is referenced, the member methods/properties of that component are made available in the [Dynamsoft Namespace](#the-dynamsoft-namespace) and can later be used by the `WebTwain` instances. -> Note: As mentioned above, if you use any of the `min` file from the `dwt` package, all add-on components are included by default. +If you use any of the `min` file from the `dwt` package, all add-on components are included by default. ## Loading the supporting files -Once the main JavaScript files are loaded in, the initialization process now moves to loading all the other supporting JS files as well as the CSS files. Depending on the mode `DWT` operates in, the supporting files vary. - -### Desktop Service Edition files - -Desktop Service Edition requires the following files found in the **Resources** folder: - -- `dynamsoft.webtwain.install.js` -- `src/dynamsoft.viewer.js` -- `src/dynamsoft.viewer.css` -- `src/dynamsoft.webtwain.css` - -#### `dynamsoft.webtwain.install.js` - -This file is used to configure the dialogs which show up when the Dynamsoft Service is not installed or needs upgrade, etc. This file is automatically loaded when the code in `dynamsoft.webtwain.initiate.js` executes. Therefore, it does not need to be referenced in the HTML page. - -> Note: As mentioned above, if you use any of the `min` file from the `dwt` package, this `install` file is already included. - -#### `dynamsoft.viewer.js`, `dynamsoft.viewer.css` and `dynamsoft.webtwain.css` - -These three files are used to build the viewer component of Dynamic Web TWAIN, as well as define the CSS of the other UI elements of the library. - -### WebAssembly Edition specific files +Once the main JS files are loaded in, the initialization process moves to load all the other supporting JS files as well as the CSS files. -Apart from the 4 files that the service mode requires, the WebAssembly Edition also needs the following files: +The following files which can be found in the **Resources** folder are required: -for image IO (decoding and encoding included) - -- `dynamsoft.imageio.js` -- `dynamsoft.imageio_wasm-.js` -- `dynamsoft.imagecore-.wasm` -- `dynamsoft.imageio-.wasm` -- `dynamsoft.imageProc-.wasm` - -for PDF reading & writing - -- `dynamsoft.pdfReader-.wasm` -- `dynamsoft.pdfWriter-.wasm` - -> These 7 files are loaded only when the first `WebTwain` instance in WebAssembly Edition is created. - -**Q: Are all 7 files mentioned above used exclusively in WebAssembly Edition** - -**A**: No, the library will use the WebAssembly files even in service mode when one of the following conditions is met - -* The APIs for the [ `WebTwain.Addon.Camera` ]({{site.info}}api/Addon_Camera.html) component are called. - -* The APIs [ `WebTwain.Camera.showVideo()` ]({{site.info}}api/Addon_Camera.html#showvideo) or [ `WebTwain.Camera.closeVideo()` ]({{site.info}}api/Addon_Camera.html#closevideo) are called. +- `dynamsoft.webtwain.install.js`: used to configure the dialogs which show up when the Dynamsoft Service is not installed or needs upgrade, etc. This file is automatically loaded when the code in `dynamsoft.webtwain.initiate.js` executes. +- `src/dynamsoft.viewer.js`, `src/dynamsoft.viewer.css`, `src/dynamsoft.webtwain.css`: used to build the viewer component of Dynamic Web TWAIN, as well as define the CSS of the other UI elements of the library. ## Creating the WebTwain instance This is the last step of the initialization. -The leading player of `DWT` is the `WebTwain` "class". Almost all methods and properties are defined in this "class". As [mentioned previously](#installation-of-the-dynamsoft-service), creating a `WebTwain` instance in Service mode requires a successful connection to the Dynamsoft Service. On the other hand, creating a `WebTwain` instance in WASM mode requires these [extra files](#wasm-specific-files). - -Read on to learn the three methods to instantiate `DWT` . - -### [ `Dynamsoft.DWT.Load` ]({{site.info}}api/Dynamsoft_WebTwainEnv.html#load) +The leading player of Dynamic Web TWAIN is the `WebTwain` class. Almost all methods and properties are defined in this class. -This is the default method to create `WebTwain` instances. +Three methods to instantiate Dynamic Web TWAIN: -#### Questions +### [`Dynamsoft.DWT.Load()`]({{site.info}}api/Dynamsoft_WebTwainEnv.html#load) -##### Q: Is it necessary to call `Dynamsoft.DWT.Load` manually +This is the default method to create `WebTwain` instances. The following two snippets are equivalent. -**A**: No. It needs to be called only if `Dynamsoft.DWT.AutoLoad` is set to `false` . If `AutoLoad` is `true` , `Load` will be called automatically as soon as the running environment is ready. - -`Dynamsoft.DWT.AutoLoad` is defined in the file `dynamsoft.webtwain.config.js` but can be called anywhere before the actual loading begins. It is set to `true` by default. - -##### Q: Where can I get the handler(s) of the instance(s) - -**A**: When `Load` is called, `DWT` tries to create the `WebTwain` instances. Once it's done, `DWT` triggers the built-in callback `Dynamsoft.DWT.OnWebTwainReady` in which the method [ `Dynamsoft.DWT.GetWebTwain` ]({{site.info}}api/Dynamsoft_WebTwainEnv.html#getwebtwain) can be used to get the handler(s) of the instance(s). For simplicity, the `OnWebTwainReady` callback points to a global function called `Dynamsoft_OnReady` . The following snippets are equivalent - -Snippet one +Snippet 1: ``` javascript Dynamsoft.DWT.OnWebTwainReady = function() { @@ -170,7 +65,7 @@ Dynamsoft.DWT.OnWebTwainReady = function() { } ``` -Snippet two +Snippet 2: ``` javascript Dynamsoft.DWT.RegisterEvent('OnWebTwainReady', Dynamsoft_OnReady); @@ -179,71 +74,16 @@ function Dynamsoft_OnReady() { } ``` -##### Q: How can I customize the instances +By default, `Dynamsoft.DWT.Load()` will be called automatically as soon as the running environment is ready. -**A**: The instances are defined by this line in `dynamsoft.webtwain.config.js` +You can control the behavior using `Dynamsoft.DWT.AutoLoad` which is defined in the file `dynamsoft.webtwain.config.js`. It is set to `true` by default but can be called anywhere before the actual loading begins. -``` javascript -Dynamsoft.DWT.Containers = [{ - ContainerId: 'dwtcontrolContainer', - Width: '585px', - Height: '513px' -}]; -``` - -> Note that `Containers` is an array of the `Container` type - -``` typescript -interface Container { - WebTwainId?: string; - ContainerId?: string; - Width?: string | number; - Height?: string | number; -} -``` - -`WebTwainId` and `ContainerId` are both optional but one must exist as the identifier for that `WebTwain` instance. - -`Width` and `Height` determine the initial viewer size of the instance. +When `Load()` is called, `DWT` tries to create the `WebTwain` instances. Once it's done, `DWT` triggers the built-in callback `Dynamsoft.DWT.OnWebTwainReady` in which the method [`Dynamsoft.DWT.GetWebTwain`]({{site.info}}api/Dynamsoft_WebTwainEnv.html#getwebtwain) can be used to get the handler(s) of the instance(s). For simplicity, the `OnWebTwainReady` callback points to a global function called `Dynamsoft_OnReady`. -When instantiating with `Dynamsoft.DWT.Load` , `ContainerId` , `Width` and `Height` are required. `DWT` will try to locate an HTML element with the id defined by `ContainerId` and use `Width` and `Height` as the viewer size. - -To create multiple instances, simply provide multiple `Containers` , for example, the following creates two `WebTwain` instances - -``` javascript -Dynamsoft.DWT.Containers = [{ - ContainerId: 'dwtcontrolContainer1', - Width: '585px', - Height: '513px' -}, { - ContainerId: 'dwtcontrolContainer2', - Width: '585px', - Height: '513px' -}]; -``` - -### [ `Dynamsoft.DWT.CreateDWTObject` ]({{site.info}}api/Dynamsoft_WebTwainEnv.html#createdwtobject) +### [`Dynamsoft.DWT.CreateDWTObject()`]({{site.info}}api/Dynamsoft_WebTwainEnv.html#createdwtobject) This method manually creates a `WebTwain` instance with a default built-in viewer. -#### Questions - -##### Q: Can this method create a `WebTwain` instance that does not come with a default viewer - -**A**: No, only [ `CreateDWTObjectEx` ](#dynamsoftwebtwainenvcreatedwtobjectex) can do that. - -##### Q: Can this method be used alongside [Load](#dynamsoftwebtwainenvload) - -**A**: Yes, this method can create more `WebTwain` instances after [Load](#dynamsoftwebtwainenvload) has created the initial one. - -##### Q: How do I use this method to create `WebTwain` instances without using [Load](#dynamsoftwebtwainenvload) - -**A**: [Load](#dynamsoftwebtwainenvload) is called automatically if `Dynamsoft.DWT.AutoLoad` is set to `true` . Therefore, to ignore [Load](#dynamsoftwebtwainenvload), `Dynamsoft.DWT.AutoLoad` must be set to `false` . - -##### Q: How do I use `CreateDWTObject` - -**A**: This method has the following syntax - ``` javascript /** * Create a WebTwain instance with UI. @@ -279,43 +119,12 @@ Dynamsoft.DWT.CreateDWTObject( ); ``` -The method can also do something that [Load](#dynamsoftwebtwainenvload) can't. The following code creates a `WebTwain` instance that connects to the Dynamsoft Service running on another machine with the IP 192.168.8.221 and ports 18622 and 18623 (SSL) +The method can also do something that [Load](#dynamsoftwebtwainenvload) can't. The following code creates a `WebTwain` instance that connects to the Dynamsoft Service running on another machine. Check out [how to enable remote scan]({{site.indepth}}faq/how-to-enable-remote-scan.html). -> NOTE that [ `Dynamsoft.DWT.UseLocalService` ]({{site.info}}api/Dynamsoft_WebTwainEnv.html#uselocalservice) must be `true` for this usage. - -``` javascript -Dynamsoft.DWT.UseLocalService = true; -Dynamsoft.DWT.CreateDWTObject( - 'dwtcontrolContainer', - "192.168.8.221", - "18622", "18623" - function(obj) {}, - function(err) { - console.log(err); - } -); -``` - -For more information, check out [how to enable remote scan]({{site.indepth}}features/input.html#how-to-enable-remote-scan). - -### [ `Dynamsoft.DWT.CreateDWTObjectEx` ]({{site.info}}api/Dynamsoft_WebTwainEnv.html#createdwtobjectex) +### [`Dynamsoft.DWT.CreateDWTObjectEx()`]({{site.info}}api/Dynamsoft_WebTwainEnv.html#createdwtobjectex) This method manually creates a `WebTwain` instance without a default built-in viewer. -#### Questions - -##### Q: Can this method be used alongside [Load](#dynamsoftwebtwainenvload) - -**A**: Yes, same as [ `CreateDWTObject` ](#dynamsoftwebtwainenvcreatedwtobject). - -##### Q: How do I use this method to create `WebTwain` instances without using [Load](#dynamsoftwebtwainenvload) - -**A**: Same as [ `CreateDWTObject` ](#dynamsoftwebtwainenvcreatedwtobject). - -##### Q: How to use `CreateDWTObjectEx` - -**A**: This method has the following syntax - ``` typescript /** * Create a WebTwain instance without UI. @@ -330,7 +139,7 @@ CreateDWTObjectEx( ): void; ``` -The following is the interface `DWTInitialConfig` +The following is the `DWTInitialConfig` interface: ``` typescript interface DWTInitialConfig { @@ -341,11 +150,11 @@ interface DWTInitialConfig { } ``` -Compared with [ `CreateDWTObject` ](#dynamsoftwebtwainenvcreatedwtobject), `CreateDWTObjectEx` requires a `WebTwainId` instead of a `ContainerId` . +Compared with [`CreateDWTObject`](#dynamsoftwebtwainenvcreatedwtobject), `CreateDWTObjectEx` requires a `WebTwainId` instead of a `ContainerId`. The following would be equivalent to using [Load](#dynamsoftwebtwainenvload) with the configuration `Dynamsoft.DWT.Containers = [{ContainerId: 'dwtcontrolContainer', Width: '585px', Height: '513px'}` -> NOTE that the created instance doesn't have a built-in viewer but instead used the method [ `bind()` ]({{site.info}}api/WebTwain_Viewer.html#bind) to add a viewer. +The created instance doesn't have a built-in viewer. You can instead use the method [`bind()`]({{site.info}}api/WebTwain_Viewer.html#bind) to add a viewer. ``` javascript var DWObject = null; @@ -365,26 +174,50 @@ Dynamsoft.DWT.CreateDWTObjectEx({ ); ``` -Similar to [ `CreateDWTObject` ](#dynamsoftwebtwainenvcreatedwtobject), `CreateDWTObjectEx` can also connect to the Dynamsoft Service running on another machine +Similar to [`CreateDWTObject`](#dynamsoftwebtwainenvcreatedwtobject), `CreateDWTObjectEx` can also connect to the Dynamsoft Service running on another machine. Check out [how to enable remote scan]({{site.indepth}}faq/how-to-enable-remote-scan.html). -> NOTE that `Dynamsoft.DWT.UseLocalService` must be `true` for this usage. +## Customizing the instances + +The instances are defined in `dynamsoft.webtwain.config.js`: ``` javascript -Dynamsoft.DWT.UseLocalService = true; -Dynamsoft.DWT.CreateDWTObjectEx({ - WebTwainId: 'dwtcontrolContainer1', - Host: "192.168.8.221", - Port: "18622", - SSLPort: "18623" - }, - function(obj) {}, - function(err) { - console.log(err); - } -); +Dynamsoft.DWT.Containers = [{ + ContainerId: 'dwtcontrolContainer', + Width: '585px', + Height: '513px' +}]; +``` + +`Containers` is an array of the `Container` type. + +``` typescript +interface Container { + WebTwainId?: string; + ContainerId?: string; + Width?: string | number; + Height?: string | number; +} ``` -For more information, check out [how to enable remote scan]({{site.indepth}}features/input.html#how-to-enable-remote-scan). +Notes: + +- `WebTwainId` and `ContainerId` are both optional but one must exist as the identifier for that `WebTwain` instance. +- `Width` and `Height` determine the initial viewer size of the instance. +- When instantiating with `Dynamsoft.DWT.Load` , `ContainerId` , `Width` and `Height` are required. Dynamic Web TWAIN will try to locate an HTML element with the ID defined by `ContainerId` and use `Width` and `Height` as the viewer size. + +To create multiple instances, simply provide multiple `Containers`. For example, the following code creates two `WebTwain` instances: + +``` javascript +Dynamsoft.DWT.Containers = [{ + ContainerId: 'dwtcontrolContainer1', + Width: '585px', + Height: '513px' +}, { + ContainerId: 'dwtcontrolContainer2', + Width: '585px', + Height: '513px' +}]; +``` ## The Dynamsoft Namespace @@ -392,14 +225,14 @@ Dynamic Web TWAIN operates under the `Dynamsoft` namespace. `Dynamsoft` is the top-level namespace. Dynamic Web TWAIN and other Dynamsoft libraries are all defined under `Dynamsoft`. For Dynamic Web TWAIN, the major members of this namespace are: -* [`DWT`]({{site.info}}api/Dynamsoft_WebTwainEnv.html) +- [`DWT`]({{site.info}}api/Dynamsoft_WebTwainEnv.html) - Includes global methods, properties to help with `WebTwain` initialization and instantiation, etc. as shown in previous context. + Includes global methods, properties for `WebTwain` initialization and instantiation, etc. -* `Lib` +- `Lib` Includes information like environment detection results (`Dynamsoft.Lib.env`) and global methods like `showMask()`, `hideMask()`, etc. -* `Enumerations` +- `Enumerations` - Example: [`Dynamsoft.DWT.EnumDWT_PixelType`]({{site.info}}api/Dynamsoft_Enum.html#dynamsoftenumdwt_pixeltype) + Includes enumerations like [`Dynamsoft.DWT.EnumDWT_PixelType`]({{site.info}}api/Dynamsoft_Enum.html#dynamsoftenumdwt_pixeltype). diff --git a/info/api/Dynamsoft_Enum.md b/info/api/Dynamsoft_Enum.md index 40508b9b..cae5b335 100644 --- a/info/api/Dynamsoft_Enum.md +++ b/info/api/Dynamsoft_Enum.md @@ -1,13 +1,14 @@ --- layout: default-layout needAutoGenerateSidebar: true +noTitleIndex: true title: Dynamic Web TWAIN API Reference - Enumerations keywords: Dynamic Web TWAIN, Documentation, API Reference, Enumerations breadcrumbText: Enumerations description: Dynamic Web TWAIN SDK Documentation API Reference Enumerations Page --- -# `Enumerations` +# Enumerations ## `Dynamsoft.DWT.EnumDWT_PixelType` @@ -27,7 +28,7 @@ description: Dynamic Web TWAIN SDK Documentation API Reference Enumerations Page | TWPT_SCRGB | 11 | | TWPT_INFRARED | 16 | -## `Dynamsoft.DWT.EnumDWT_BorderStyle ` +## `Dynamsoft.DWT.EnumDWT_BorderStyle` | Label | Value| |:-|:-| @@ -35,7 +36,7 @@ description: Dynamic Web TWAIN SDK Documentation API Reference Enumerations Page | TWBS_SINGLEFLAT | 1 | | TWBS_SINGLE3D | 2 | -## `Dynamsoft.DWT.EnumDWT_MessageType ` +## `Dynamsoft.DWT.EnumDWT_MessageType` | Label | Value| |:-|:-| @@ -201,7 +202,7 @@ description: Dynamic Web TWAIN SDK Documentation API Reference Enumerations Page | TWON_ONEVALUE | 5 | | TWON_RANGE | 6 | -## `Dynamsoft.DWT.EnumDWT_TransferMode ` +## `Dynamsoft.DWT.EnumDWT_TransferMode` | Label | Value| |:-|:-| @@ -209,7 +210,7 @@ description: Dynamic Web TWAIN SDK Documentation API Reference Enumerations Page | TWSX_FILE | 1 | | TWSX_MEMORY | 2 | -## `Dynamsoft.DWT.EnumDWT_FileFormat ` +## `Dynamsoft.DWT.EnumDWT_FileFormat` | Label | Value| Description | |:-|:-|:-| @@ -230,7 +231,7 @@ description: Dynamic Web TWAIN SDK Documentation API Reference Enumerations Page | TWFF_PDFA | 15 | A file format from Adobe PDF/A, Version 1 (TWAIN Spec 2.0) | | TWFF_PDFA2 | 16 | A file format from Adobe PDF/A, Version 2 (TWAIN Spec 2.1) 、 -## `Dynamsoft.DWT.EnumDWT_TIFFCompressionType ` +## `Dynamsoft.DWT.EnumDWT_TIFFCompressionType` | Label | Value| |:-|:-| @@ -245,7 +246,7 @@ description: Dynamic Web TWAIN SDK Documentation API Reference Enumerations Page | TIFF_JPEG | 7 | | TIFF_PACKBITS | 32773 | -## `Dynamsoft.DWT.EnumDWT_InterpolationMethod ` +## `Dynamsoft.DWT.EnumDWT_InterpolationMethod` | Label | Value| |:-|:-| @@ -254,7 +255,7 @@ description: Dynamic Web TWAIN SDK Documentation API Reference Enumerations Page | IM_BICUBIC | 3 | | IM_BESTQUALITY | 5 | -## `Dynamsoft.DWT.EnumDWT_ImageType ` +## `Dynamsoft.DWT.EnumDWT_ImageType` | Label | Value| |:-|:-| @@ -269,7 +270,7 @@ description: Dynamic Web TWAIN SDK Documentation API Reference Enumerations Page Note: IT_MULTIPAGE_PDF & IT_MULTIPAGE_TIF are only applicable to the ImageType of [startScan]({{site.info}}api/WebTwain_Acquire.html#startscan) -## `Dynamsoft.DWT.EnumPDF_Page ` +## `Dynamsoft.DWT.EnumPDF_Page` | Label | Value| |:-|:-| @@ -295,7 +296,7 @@ Note: IT_MULTIPAGE_PDF & IT_MULTIPAGE_TIF are only applicable to the ImageType o | PDF_JP2000 | 6 | | PDF_JBig2 | 7 | -## `Dynamsoft.DWT.EnumDWT_ShowMode ` +## `Dynamsoft.DWT.EnumDWT_ShowMode` | Label | Value| |:-|:-| @@ -305,7 +306,7 @@ Note: IT_MULTIPAGE_PDF & IT_MULTIPAGE_TIF are only applicable to the ImageType o | SW_CLOSE | 3 | | SW_IFLIVE | 4 | -## `Dynamsoft.DWT.EnumDWT_CapValueType ` +## `Dynamsoft.DWT.EnumDWT_CapValueType` | Label | Value| |:-|:-| @@ -323,7 +324,7 @@ Note: IT_MULTIPAGE_PDF & IT_MULTIPAGE_TIF are only applicable to the ImageType o | TWTY_STR128 | 11 | | TWTY_STR255 | 12 | -## `Dynamsoft.DWT.EnumDWT_UnitType ` +## `Dynamsoft.DWT.EnumDWT_UnitType` | Label | Value| |:-|:-|