Let us see:daisensou wrote:The pathfield does not expand to fit a bigger path, at least, it never did expand in all my tests.thibaud wrote:would it not occur to any of you that the texfield content plays a major role here...
none of the screenshots shows a usability issue (path cropped).
I don't see no problems.
The issue is wasted space, such a small text field is 'useless'. If you re-size the XnView window so it uses 2-rows instead, you will see the pathfield expand or contract accordingly. That one should be the expected behavior.
But this is such an elusive problem, that I truly don't know what else to do. Pierre can't replicate it, yet it always happens to me, doesn't matter the OS I use. This weekend I may get my hands on a Mac and I'll try to run some tests there too.
You see this:
...and Pierre sees this:
...and this is because, as you tried to explain here, it depends on how XnViewMP is started.
I can reproduce this in 100% from cases, just be sure to have the path long enough to get out from the address field!
If XnView MP is started by double-clicking on the icon, then the address field is wide.
If XnView MP is started by right-clicking on a folder and choosing "Browse with XnView MP", then the address field is narrow.
Pierre, perhaps you do some custom processing with the width of the address field when a file / folder is passed as a command line argument?