[bug] Inserting a page during OCR inserts the page, but (…)

[Jensen Head]

(…) hides the progress bar and leaves the app UI locked (~ for some unknown reason) until the OCR is complete (which happens in the background with no visual indication of the process or ETA).
͏
PDF-XChange Editor 10.6.0, build 396
Microsoft Windows 10.0.19045.6036

[Daniel - PDF-XChange]

Hello, Jensen Head

In the future, it might be a good idea to include a bit more of an explanation on the process to reproduce such issues. It took me a while to try drag/drop into the thumbnails pane specifically... For all other methods of inserting pages, OCR blocks other actions while running... So I was about to ask how exactly are were inserting a page during OCR in the first place.

Now that I have reproduced it, I can confidently say this is not an intended function, and should not work at all. So when I report this it is likely to be blocked entirely, until we are able to allow OCR and other long term functions to run entirely in the background during normal editing.

RT#7567: Bug: DnD to thumbnails during OCR - progress bar vanish.

Kind regards,

[Jensen Head]

In the future, it might be a good idea to include a bit more of an explanation on the process to reproduce such issues.

I understand you. For me, it's a constant choice between "by the time I finished reading this huge post, I'd already forgotten the beginning" / "why did you write so many letters when a concisely and clearly formulated problem exhaustively reports what's needed?!" and "the person on the other end of the line has no idea about you, your tasks, documents, and the conditions of work on them; write as if for an alien from a galaxy far, far away." On platforms with built-in bug trackers, templates for issues help. They clearly answer the question of in what form exactly developers prefer to receive bug reports and FRs.

[Daniel - PDF-XChange]

Hello, Jensen Head

That is understandable, it is a hard balancing act. We dont usually need full winded comprehensive breakdowns. Usually 1-3 sentences is enough to convey the process. With the most important parts being "How (exactly) do I do it again?" and "What happens when I do it?"
Questions like, "how else can I do it", and "what happens if I do it this way instead" are excellent speculation (and those are usually what leads to an extensive dissertation), but not strictly necessary for a quick report like this.

EG, if I was writing your initial report, it would look something like this: (Infact this is how I re-summarized it to the Dev team internally)

When dragging/dropping a file to "insert pages" via the thumbnails pane of a file being processed by OCR pages, the pages are properly inserted into the document. However, in doing so, the OCR pages progress bar disappears, leaving the Editor seemingly frozen until it finishes processing OCR on the document.

Your report was nearly complete, you only left out the key "cause/reproduction action", in the first statement "Drag and drop of a file into the thumbnails pane"

Kind regards,