Ready-to-use UI (DocScanningSDK-UI) Pixelnetica™ Document Scanning SDK for Apple iOS

This is the map of the DocScanningSDK-UI ready-to-use screen API. The full generated reference is published alongside these pages. This layer is Swift; each screen ships as a UIKit controller and a SwiftUI wrapper, with a configuration object and a result/delegate.

The screens

Screen (SwiftUI wrapper)ConfigurationResult / delegateGuide
PxUiCameraScreen (PxUiCameraScreenView)PxUiCameraScreenConfigurationPxUiCameraScreenResult / PxUiCameraScreenDelegateCamera capture
PxUiPageCropScreen (PxUiPageCropScreenView)PxUiPageCropScreenConfigurationPxUiPageCropScreenResult / PxUiPageCropScreenDelegateEdge detection & cropping
PxUiOcrEditorScreen (PxUiOcrEditorScreenView)PxUiOcrEditorScreenConfigurationPxUiOcrEditorScreenResult / PxUiOcrEditorScreenDelegateOCR & text recognition
PxUiLanguagePickerScreen (PxUiLanguagePickerScreenView)PxUiLanguagePickerScreenConfigurationPxUiLanguagePickerScreenResult / PxUiLanguagePickerScreenDelegateOCR languages

Each SwiftUI wrapper takes the inputs its screen needs — a configuration, plus a picture and cutout for the crop editor, or a PxUiOcrEditorSession for the OCR editor — and calls back with the result; the UIKit controller uses the matching delegate. The language picker additionally exposes PxUiLanguagePickerSelection and a PxUiLanguagePickerSelectionStore for persisting the selection.

Customisation

On-screen text is overridable and localisable through the strings table — see Customising the ready-to-use UI. Per-screen behaviour is set through each screen’s *Configuration.

See also

Top