What a pain!

What a pain!

[David Arnold]

All,

I have Acrobat Reader 4.0. Everytime I compile junk.tex to junk.pdf, I have
to have the file junk.pdf closed in AR4. What a pain.

Is there anyway to leave junk.pdf open in AR4, compile junk.tex to
junk.pdf, then have the result displayed in AR4?

Re: What a pain!

[Hans Hagen]

David Arnold wrote:

> I have Acrobat Reader 4.0. Everytime I compile junk.tex to junk.pdf, I have
> to have the file junk.pdf closed in AR4. What a pain.
> 
> Is there anyway to leave junk.pdf open in AR4, compile junk.tex to
> junk.pdf, then have the result displayed in AR4?

No. This is reported frequently to Adobe. The linux viewer does not lock
the file. You can also use GhostView, which does not lock the file,
latest version, with GS >=5.50. Hyperlinks work, but widgets don't.
Graphics show up far better. 

Hans

-----------------------------------------------------------------
                                          Hans Hagen | PRAGMA ADE
              Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
      tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.nl
-----------------------------------------------------------------

Re: What a pain!

[Hans Hagen]

Taco Hoekwater wrote:

>     David> Is there anyway to leave junk.pdf open in AR4, compile
>     David> junk.tex to junk.pdf, then have the result displayed in
>     David> AR4?
> 
> No. All versions of Reader under Windows behave this way. Linux
> version is slightly better: there is no lock on the pdf file, so that
> compiling works, but you still need to close and re-open to get at the
> new file.

Maybe this is due to page caching and loading of the reference table. It
is interesting to see than dvi and ps viewers are better in this. 

Hans

-----------------------------------------------------------------
                                          Hans Hagen | PRAGMA ADE
              Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
      tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.nl
-----------------------------------------------------------------

Re: What a pain!

[Taco Hoekwater]

>>>>> "David" == David Arnold <darnold@northcoast.com> writes:

    David> All, I have Acrobat Reader 4.0. Everytime I compile
    David> junk.tex to junk.pdf, I have to have the file junk.pdf
    David> closed in AR4. What a pain.

    David> Is there anyway to leave junk.pdf open in AR4, compile
    David> junk.tex to junk.pdf, then have the result displayed in
    David> AR4?

No. All versions of Reader under Windows behave this way. Linux
version is slightly better: there is no lock on the pdf file, so that
compiling works, but you still need to close and re-open to get at the 
new file.

Taco

Re: What a pain!

[Taco Hoekwater]

>>>>> "Hans" == Hans Hagen <pragma@wxs.nl> writes:

    Hans> David Arnold wrote:
    >> I have Acrobat Reader 4.0. Everytime I compile junk.tex to
    >> junk.pdf, I have to have the file junk.pdf closed in AR4. What
    >> a pain.
    >> 
    >> Is there anyway to leave junk.pdf open in AR4, compile junk.tex
    >> to junk.pdf, then have the result displayed in AR4?

    Hans> No. This is reported frequently to Adobe. The linux viewer
    Hans> does not lock the file. You can also use GhostView, which
    Hans> does not lock the file, latest version, with GS
    Hans> >=5.50. Hyperlinks work, but widgets don't.  Graphics show
    Hans> up far better.

As well as far slower...

Taco

Re: What a pain!

[Taco Hoekwater]

>>>>> "Hans" == Hans Hagen <pragma@wxs.nl> writes:

    Hans> Taco Hoekwater wrote:
    David> Is there anyway to leave junk.pdf open in AR4, compile
    David> junk.tex to junk.pdf, then have the result displayed in
    David> AR4?
    >>  No. All versions of Reader under Windows behave this
    >> way. Linux version is slightly better: there is no lock on the
    >> pdf file, so that compiling works, but you still need to close
    >> and re-open to get at the new file.

    Hans> Maybe this is due to page caching and loading of the
    Hans> reference table. It is interesting to see than dvi and ps
    Hans> viewers are better in this.

It's technically doable though, since VTeX does have the redraw
working (by controlling the Reader through (undocumented) DDE calls).

Taco

Re: What a pain!

[Tobias Burnus]

Hallo and hi,

> > I have Acrobat Reader 4.0. Everytime I compile junk.tex to junk.pdf, I have
> > to have the file junk.pdf closed in AR4. What a pain.
> > Is there anyway to leave junk.pdf open in AR4, compile junk.tex to
> > junk.pdf, then have the result displayed in AR4?
> 
> No. This is reported frequently to Adobe. The linux viewer does not lock
> the file. You can also use GhostView, which does not lock the file,
> latest version, with GS >=5.50. Hyperlinks work, but widgets don't.
> Graphics show up far better.

Under Linux AR doesn't lock the file, so after you have TeXed the file
you can do File|Close; Go back (I think Ctrl-w, Ctrl-< (or was it Ctrl-'-'?))

Under Windows, you must do 'File|Close' -- TeX -- 'View(?)|Go back';
going back has the advantage that you will go to the same page, which you left
when closing (instead of the first page with default zoom).

Tobias

PS: Sorry I haven't a open AR at the moment so take care with the statements ;-)

Re: What a pain!

[Tobias Burnus]

Hi,

> >     David> Is there anyway to leave junk.pdf open in AR4, compile
> >     David> junk.tex to junk.pdf, then have the result displayed in
> >     David> AR4?
> > No. All versions of Reader under Windows behave this way. Linux
> > version is slightly better: there is no lock on the pdf file, so that
> > compiling works, but you still need to close and re-open to get at the
> > new file.
> Maybe this is due to page caching and loading of the reference table. It
> is interesting to see than dvi and ps viewers are better in this.

Well you can browse (under linux) without reloading the file, but only
until AR finds out that the references doesn't fit any more; then you
get an error message, a blank page (or a gray background, the file is 
nethertheless still open).

In Windows there is hook, so you get a WM_<file modified> message, when
a file had been change; under Linux/unix I don't know, but XDVI does
check the file, when the window regets the focus and if it reads from
the file; so all Adobe needs to do is a file date check mechanismus:

if (old_filedate isOlderThan new_filedate)
then old_filedate := new_filedate
     reload_references etc;
     redisplay

Tobias