Version: (using Devel) Installed from: Compiled sources OS: Linux When clicking on a PDF link to the same document okular correctly seeks the link destination and displays the wanted page. If now you click the previous button (top left), I'd guess you should be able to go the latest position before jumping to the link destination. But the current implementation just goes back one page. Since we have the green (bottom center) buttons and the thumbnails view for changing page, I think the implementation of the top left Prev/Next buttons could be changed.
Don't understand why they "seem to be useless". They make you go to the previous or next page, as their tooltip say. Why should the implementation of prev/next page be changed? And what to??
Hi Pino, replaying to #1 okular has many ways to go to the previous next page (buttons at top, at bottom, mouse dragging, mouse wheel, thmbnails) but no way to go back to the last page visited before clicking a link. Browsers and filemanagers have set the de facto standard of having a prev/next button in the same position has (top left). I think it is not useful and misleading to have the top left buttons behaving differently from how they behave on most of other applications... but I'm not an usability expert. OTHA we already have a couple of prev/next buttons at the bottom of the gui... why two pairs of buttons? I hope I managed to express my POV :-) Vincenzo
> Browsers and filemanagers have set the de facto standard of having a prev/next button in the same position has (top left). Okular is not a file managers, and not even a browser. > I think it is not useful and misleading to have the top left buttons behaving differently from how they behave on most of other applications... In KPDF, in that position there are the prev/next _history_ buttons, and people complained that it was not for navigating... Now people think they should be for navigating... that's is just a mess, mainly on what users request, really. > but no way to go back to the last page visited before clicking a link. Ah! Then _this_ is the right issue? Please tell that before, better than labelling "prev/next is useless".....
>In KPDF, in that position there are the prev/next _history_ buttons, and people >complained that it was not for navigating... Now people think they should be for >navigating... that's is just a mess, mainly on what users request, really. I understand making all users happy with the same setup is not easy :-) Okular is just impressive at the moment: it is fast, does its job right and is really nice looking IMHO. BTW, if people complain about that buttons, what about completely getting rid of them? There is not added functionality in having them IMHO. >> but no way to go back to the last page visited before clicking a link. > Ah! Then _this_ is the right issue? Please tell that before, better than labelling "prev/next is useless"..... Well, this is part of the issue :-) the other part is that having those buttons makes some people (me at least) think that the functionality is present, while it isn't.
When was decided we would kill the viewport history navigation? I'm completely against this
The prev/next history navigation buttons are common to almost all modern hyperlinked content viewers, not just file managers and browsers.
ok, so back/fordward in history is still on the menu, remove comment #5 :D
I support that issue - quite confusing if you read a hyperlink document and whant to go "back"...
Sorry guys, the toolbar setup won't be changed. But the icons will, since it is presumably them that are causing the confusion. The "next/previous page" toolbar icons look like those "back/forward" actions we all know so well from web browsers. And in fact Okular is even offering these actions with the exact same icons as "previous/next". So what we are going to do is take the "previous/next bookmark" icons and use them for the "next/previous page" actions. They feature a page with an "Up", respectively "Down" arrow on a paper sheet and much better transport the message what a click on them is doing.
So there won't be any "back" and "forward" action like in kpdf and Adobe Reader? IMHO hyperlinks are then quite useless... And as somebody said before we have the next/previous page buttons already in the bottom in green. Is there any specific reason not to implement (additional) "back/forward" buttons?
> So there won't be any "back" and "forward" action like in kpdf and Adobe Reader? The functionality is there (See the Go-menu and look there for "back/forward in the document"), it just won't be in the toolbar by default, at least not for now. However you are still able to add these actions to the toolbar by yourself. > And as somebody said before we have the next/previous page buttons already in the bottom in green. If anything, then the buttons at the bottom in green should go. But that's too much to discuss for one bug report. > Is there any specific reason not to implement (additional) "back/forward" buttons? Yes, mainly limited toolbar space which gets even worse if you use languages different from English.
If you must have duplicate page flip buttons, please use the same icons. Having two different-looking pairs of arrow buttons is a very strong queue that one flips pages and the other navigates history. (IMO, the better solution is to have a single set of page flip buttons placed into a standard dockable toolbar; users can place that toolbar wherever they find convenient - bug 157284.)
Ok, I see. I changed the buttons and prefer that setting a lot. The green buttons on the bottom are quite intuitive, but as kde2eran said, some dockable toolbar might be even better. I understand the language-issue and don't want to insist, I just wanted to express a users preference.
I close this bug: I've got used to the ui (I changed the the buttons to prev/next behavior). Okular rocks so much! Many tnx to all the people involved in coding it :-)