XnView Software

xnview wrote:Why you don't use layout save/restore??

There would be too many separate layouts to cover all usage modes. Plus there is as yet no method to name layouts, so it is troublesome to remember which is which and what they do.

Yes, MP layouts are more "flexible" than 1.9x, but that is barely relevant to my use. Many here in the forum remember that it took years of testing and iterative design to get 1.9x to its current excellent state. It works the way I require it to, better than any other software. But at least for now, MP cannot be made to behave the way 1.9x does, so either I must change the way I work (not likely, and for what benefit?) or decline to use MP. The latter option is regretted because MP already has many new useful features.

For fluid use of MP there needs to be better flow between layouts and a more logical, simpler control over the visibility of the browser panels. That is why I suggested the specific improvements posted above (and in my PM to you).

For me, 1.9x better addresses my image workflow, so I have been trying to influence your efforts for MP toward the 1.9x design.

JohnFredC wrote:

xnview wrote:Why you don't use layout save/restore??

There would be too many separate layouts to cover all usage modes. Plus there is as yet no method to name layouts, so it is troublesome to remember which is which and what they do.

I can add naming of layout... What's the problem " too many separate layouts to cover all usage modes"??? Why you can't make a layout with only thumbnails view??

xnview wrote:I can add naming of layout...

That would certainly help me a lot. Plus more than 8 layouts.

xnview wrote:What's the problem " too many separate layouts to cover all usage modes"??? Why you can't make a layout with only thumbnails view??

Yes I can make an all-thumbs-layout, but the visibility of the preview/info panes still doesn't work logically with it (IMO). Perhaps fixing the Preview bug which started this thread will help.

Some of us use several layouts "in concert" (that is two or more layouts working together in sequences). The ability to move quickly to the next "logical" layout needed by the workflow is important. Perhaps a layout history would work well with "next layout" and "previous layout" commands.

JohnFredC wrote:Yes I can make an all-thumbs-layout, but the visibility of the preview/info panes still doesn't work logically with it (IMO). Perhaps fixing the Preview bug which started this thread will help.

You means that preview visibility is not always the same with menu item???

Some of us use several layouts "in concert" (that is two or more layouts working together in sequences). The ability to move quickly to the next "logical" layout needed by the workflow is important. Perhaps a layout history would work well with "next layout" and "previous layout" commands.

You ask me for the button-splitter of 1.97, but it's the same with layout, one click. No? Sorry but i don't understand

xnview wrote:You ask me for the button-splitter of 1.97, but it's the same with layout, one click. No? Sorry but i don't understand

Hi Pierre

As currently implemented, switching layouts is not an "one click" activity. Layout menu access is more of a "click-hover-click". IMO most users would prefer the one-click directness of the divider buttons in 1.9x.

Hi John,

JohnFredC wrote:

xnview wrote:You ask me for the button-splitter of 1.97, but it's the same with layout, one click. No? Sorry but i don't understand

As currently implemented, switching layouts is not an "one click" activity. Layout menu access is more of a "click-hover-click". IMO most users would prefer the one-click directness of the divider buttons in 1.9x.

And if you are able to add layout item in the toolbar? Now with the docks/panels i can't have a single divider buttons. We must find another solution... Hotkey, button in toolbar?????

Well, in that case, toolbar buttons would offer the most "direct" control for mouse users. If there were a show/hide command for each panel that a user could assign to a button?

Maybe just a cmd_HideShowPreview on a button would be enough for now. We already have buttons for the Tree and Info.

In version 0.32 user is able to reliably hide/show preview via View->Info Pane->Preview.

A great convenience!