XnView Software

Hello,

In 82 RC1 (only) PGUp or PGDown (key of the keyboard inserted) in Full screen do not show each picture... (Only the name of the picture change)...

In "Viewer" it's OK...

(With de previous release it works fine).

Is it a bug or is it a new feature ?


@+

Hello, bonsoir !

- I just tested at this moment under XP-Pro, that works perfectly…

- Which OS are you using ?

- I tested both full screen from "View" and from the browser-preview, no problem…

Kind regards,
Claude
Clo

ch3n3 wrote:Hello,

In 82 RC1 (only) PGUp or PGDown (key of the keyboard inserted) in Full screen do not show each picture... (Only the name of the picture change)...

In "Viewer" it's OK...

(With de previous release it works fine).

Is it a bug or is it a new feature ?

You press PgUp/Down only one time?

xnview wrote:You press PgUp/Down only one time?

No, I press the Key and I hold it down.

(If you take a picture from a scene, each day at the same time, and if this pictures are in the same folder, you can view in full screen the first picture, and then, with hold down the PGDown key, you can see the evolution of the scene (like a "movie" for example)

It works fine in Viewer mode...



(Sorry for my (poor) english)

It is expected behaviour, reproducible in all modes (in windowed View as well).
When you hold PageDown, rendering of the current image is interrupted and next image is rendered as next keypress is received. In effect you see only changing file names.
This was actually a requested feature.
If you want "movie", you need to press PageDown multiple times, after current image rendering is completed.

X.

ch3n3 wrote:

xnview wrote:You press PgUp/Down only one time?

No, I press the Key and I hold it down.

(If you take a picture from a scene, each day at the same time, and if this pictures are in the same folder, you can view in full screen the first picture, and then, with hold down the PGDown key, you can see the evolution of the scene (like a "movie" for example)

It works fine in Viewer mode...

Confirmed.

Xyzzy wrote: This was actually a requested feature.

Its a bug because browser's fullscreen and viewer act differently. Seeing next picture while holding down <pg down> was a requested feature in last beta round. Any change in this will be unexpected and unwelcome by many.

marsh, it acts the same way (at least for me), you see "difference" because files are rendered differently to windows and to full screen, so even on the same computer, with the same images View and fullscreen WILL differ in some way. Get a directory with a few thousand images, Open first in View and hold down PageDown. After some images you'll see only filename changing.

In last beta round there was a request to stop rendering image when next is to be displayed, for example because of keypress detected. If XnView sees keypress before anything at all is displayed, it manages to display only screen info before message to image rendering thread is passed (or something like that).

X.

I was talking about last summers' beta round. v.1.80.3-like behaviour was requested then. It was agreed that some delay was useful as a progress indicator. Besides, ch3n3 should continue the discussion before subject is closed.

The link for this beta: http://newsgroup.xnview.com/viewtopic.php?t=4430

Discussion is still opened

Well if you think there should be an option for flip-anims and delay, Suggest it. Please define also what amount of image should be rendered before jumping to next image, should any images be skipped on fast keypresses etc.

Actually long ago this option was useful, because you didn't need to wait for the whole image to render to see what it is.
Now when you jump to next image even quite quickly, PC is fast enough to render whole image. And when you keep PageDown pressed all the time, you are not able to neither browse nor skip precisely anyway.

X.

Hello,

Thank you for your answers, I didn't know that it was a request...

and I anderstand that it can be useful to "jump" some pictures !


@+

IMO this (ie. flip-anim display mode) should be a distinct option, as in case of default use (navigate between images as quick as possible) it delays operations, because whole file has to be displayed before going to the next. When images are big and/or user wants to quckly jump among them this may be a problem.

X.