Bug 357971 - [frameworks branch] Okular forward search does not update the position
Summary: [frameworks branch] Okular forward search does not update the position
Status: RESOLVED WORKSFORME
Alias: None
Product: okular
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Compiled Sources Linux
: NOR normal
Target Milestone: ---
Assignee: Okular developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-01-14 10:10 UTC by luisfe
Modified: 2016-03-01 19:42 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description luisfe 2016-01-14 10:10:28 UTC
I have a tex file "prueba.tex" compiled to pdf using synctex.

If I open the file with:

$okular --unique file:/home/luisfe/prueba.pdf#src:60/home/luisfe/prueba.tex

Okular opens the file in the desired destination. However, if the file prueba.pdf is already open, the previous command does  does not update the position of okular in the file.

$okular --unique file:/home/luisfe/prueba.pdf#src:90/home/luisfe/prueba.tex

The viewer stays in the same position

Reproducible: Always

Steps to Reproduce:
1. open a pdf file complied from tex with synctex information
2. try to move the file to a new destination from the command line/kile/gvim

Actual Results:  
The position of the file is not updated

Expected Results:  
Okular should move the view to a new destination

Compiled from sources, okular version 1.0.0 using kde applications 15.12.0
Comment 1 Albert Astals Cid 2016-01-14 10:59:15 UTC
If you're using okular 1.0.0 you are not using KDE Applications 15.12.0

Please use the proper released okular and not the frameworks branch.
Comment 2 Albert Vaca Cintora 2016-02-26 20:54:32 UTC
I just created a pdf document with two named destinations and it works with the latest version from the frameworks branch in git. Can you try it again with the latest code? If you can reproduce it, please reopen the bug and attach a document where we can test it.
Comment 3 luisfe 2016-03-01 19:42:50 UTC
I confirm that it works well with the latest version from frameworks branch