import { ChangeDetectorRef, OnDestroy } from '@angular/core'; import { FocusManagementService } from '../../focus-management.service'; import { PDFNotificationService } from '../../pdf-notification-service'; import { ResponsiveVisibility } from '../../responsive-visibility'; import * as i0 from "@angular/core"; export declare class PdfDrawEditorComponent implements OnDestroy { private readonly focusManagement; private readonly cdr; show: import("@angular/core").InputSignal; disable: import("@angular/core").InputSignal; isSelected: boolean; private PDFViewerApplication; private eventBusAbortController; constructor(notificationService: PDFNotificationService, focusManagement: FocusManagementService, cdr: ChangeDetectorRef); /** * Runs `callback` and re-renders this component. * * The callback is scheduled from a pdf.js event bus listener, which runs * outside Angular's zone, so neither zone.js nor a signal write schedules a * change detection run for us - the button kept showing the previous state * until an unrelated click happened to trigger one. The view can already be * destroyed by the time a queued callback runs, and `detectChanges()` throws * on a destroyed view, so that case is skipped. */ private asyncWithCD; private onPdfJsInit; ngOnDestroy(): void; onClick: (event?: Event) => void; static ɵfac: i0.ɵɵFactoryDeclaration; static ɵcmp: i0.ɵɵComponentDeclaration; }