XnView Software

Halo.

In both View and Full-Screen modes, if I push the keyboard "Menu" button (between the right-Alt and right-Ctrl buttons) what should happen ?
Should a pop-up menu appear (similar to the default right-click) ?

For those modes, is the default focus on the image (and put back on the image after any process) ?

Thank you

.

quapurna wrote:Halo.

In both View and Full-Screen modes, if I push the keyboard "Menu" button (between the right-Alt and right-Ctrl buttons) what should happen ?
Should a pop-up menu appear (similar to the default right-click) ?

It should. But it doesn't.

For those modes, is the default focus on the image (and put back on the image after any process) ?

Thank you

.

It should. And it seems (after 5 seconds test) to work. ...even if the 'focus' is a fuzzy thing here.

Anyway, the main problem is that when one is in Fullscreen and in View, pressing the 'Menu' key on the keyboard it should display the menu.

Funny enough, in the browser it works, at least in some widgets in which I've tested.

[... Anyway, the main problem is that when one is in Fullscreen and in View, pressing the 'Menu' key on the keyboard it should display the menu.
Funny enough, in the browser it works, at least in some widgets in which I've tested. ...]

I think, it works in Browser mode if the focus is certain, which is the requirement for the contextual menu.

In View mode, if I right click the image and click out side the contextual menu that appears; the next time I push keyboard Menu button, the contextual menu will appear. The focus has been set when I right click the image. Then, if I drag the image, the focus is lost. The same case is to the image in Preview pane of Browse mode.
That is why I wonder if the focus should always be set back to the image after any process.

I am not a programmer, though.
Thanks
.

I think, it works in Browser mode if the focus is certain, which is the requirement for the contextual menu.

Well, somewhat...

In fact there are objects in each GUI framework which can display the popup menu "automagically", (usually by assigning a property or similar) whereas there are other objects for which the programmer must write some lines of code (usually handling the OnMouseDown and/or OnKeyDown events or similar) in order to manually call the popup (myPopup.Execute - or equivalent). Also, the programmer must design the popup. It isn't a big deal but it must be done.

The 'focus' problem is usually handled by the Qt (our GUI framework). In our concrete case it is quite simple (till now) because there are no widgets to be 'focused' (there are only buttons) hence he can safely write a simple handler for myImage.OnKeyDown or, if the Image doesn't receive key events (IOW on Win it doesn't have a window handle), he can directly write the code in the big OnKeyDown handler from View mode (even if this could be a little risky in the future if we'll add some controls there - but I don't think so).

just my2c & HTH