[brailleblaster] Re: Delay when opening documents

  • From: "Vic Beckley" <vic.beckley3@xxxxxxxxx>
  • To: <brailleblaster@xxxxxxxxxxxxx>
  • Date: Thu, 23 May 2013 15:36:31 -0400

Keith,

Thanks for this nice explanation of what is going on.


Best regards from Ohio,

Vic


-----Original Message-----
From: brailleblaster-bounce@xxxxxxxxxxxxx
[mailto:brailleblaster-bounce@xxxxxxxxxxxxx] On Behalf Of Keith Creasy
Sent: Thursday, May 23, 2013 3:12 PM
To: brailleblaster@xxxxxxxxxxxxx
Subject: [brailleblaster] Re: Delay when opening documents

Hi Vic.

I suspect that the progress bar isn't coming up until after LibLouisUTDML
has finished and the tree is being built. So, all this happens before we get
a progress bar:

1. BB opens the original file.
2. The file is copied to the BB temp directory.
3. BB calls LibLouisUTDML and. It begins processing.
4. When LibLouisUTDML finishes it returns with the path to the UTD enhanced
file. BB then opens and parses the working file.

It is only after all this that we have a working DOM and the tree is
populated. The real solution is to somehow refactor all this so that we can
use a SAX parser to open the file, process the elements through
LibLouisUTDML, and build the tree. There are still some complications to a
progress bar since we really don't know how much of the file, by percentage,
we have processed.
2Keith Creasy
Software Developer
American Printing House for the Blind
KCreasy@xxxxxxx
Phone: 502.895.2405
Skype: keith537


-----Original Message-----
From: brailleblaster-bounce@xxxxxxxxxxxxx
[mailto:brailleblaster-bounce@xxxxxxxxxxxxx] On Behalf Of Vic Beckley
Sent: Thursday, May 23, 2013 3:05 PM
To: brailleblaster@xxxxxxxxxxxxx
Subject: [brailleblaster] Delay when opening documents

Over the last while, it seems there has been a significant delay added when
opening documents. I am really not sure exactly when this crept in. This
delay occurs before the progress bar comes up. Once W-E starts to speak the
progress bar, the document loads practically immediately. In fact, all W-E
has time to say is 0%. I don't know what the progress bar shows the progress
of, but what would this delay be before it comes up? Are you seeing this?
Maybe you know why it is happening. Any thoughts? 


Best regards from Ohio,

Vic





Other related posts: