[Nvda-dev] [NVDA] #475: Acrobat: Unique ID as object ID for XFAPDF

[brian gafff (Line One)]

I'd go for the most robust way, given the  fact that Adobe tend to  change 
the unexpected from time to time. Maybe a decision  is best left that way.

I still find those making adobe files have a lot to learn about tagging etc, 
even they make them, so only use  this file format when there is not other 
option.

Brian
Brian Gaff  bglists at blueyonder.co.uk- If you need to email me please send it 
to
briang1 at blueyonder.co.uk
Making sure the name 'Brian Gaff' is in the display name field.
Failure to do this may result in delays or message loss.

Some sacrifices are a fact of life in our junk mail  riddled world!
----- Original Message ----- 
From: "NVDA Trac" <trac at nvda-project.org>
Cc: <nvda-dev at lists.nvaccess.org>
Sent: Wednesday, February 03, 2010 6:00 AM
Subject: Re: [Nvda-dev] [NVDA] #475: Acrobat: Unique ID as object ID for 
XFAPDF


> #475: Acrobat: Unique ID as object ID for XFA PDF
> -------------------------------+--------------------------------------------
> Reporter:  jteh               |       Owner:  jteh
>     Type:  defect             |      Status:  accepted
> Priority:  minor              |   Milestone:  2010.1
> Component:  Virtual buffers    |     Version:  trunk
> Keywords:  AdobeGrantJul2009  |          Os:
> Blockedby:                     |    Blocking:
> -------------------------------+--------------------------------------------
>
> Comment(by jteh):
>
> IOleWindow::!GetWindow() is no faster than !WindowFromAccessibleObject().
> On a document that takes about 2 seconds to load normally, using either
> !GetWindow or !WindowFromAccessibleObject causes it to take about 5
> seconds. Interestingly, on a document that takes about 11 seconds to load
> normally, perf degrades to about 15 seconds.
>
> In any case, there is a noticeable regression in performance, particularly
> for the smaller document. We're not going to get the !ObjFromLResult thing
> for 2010.1 and I'm thinking we'd probably prefer not to regress
> performance for the majority of PDFs.
>
> One other option might be to only do this for XFA PDFs (check the read-
> only state on the document). This would involve modifying the backend
> somewhat so that we can store this info as a boolean on the backend and
> use it in fillVBuf. However, this is still pretty hacky.
>
> Mick, thoughts?
>
> -- 
> Ticket URL: <http://www.nvda-project.org/ticket/475#comment:4>
> NVDA <http://www.nvda-project.org/>
> A free and open-source screen reader for Windows
> _______________________________________________
> Nvda-dev mailing list
> Nvda-dev at lists.nvaccess.org
> http://lists.nvaccess.org/listinfo/nvda-dev


--------------------------------------------------------------------------------



No virus found in this incoming message.
Checked by AVG - www.avg.com
Version: 9.0.733 / Virus Database: 271.1.1/2664 - Release Date: 02/02/10 
19:35:00