XnView Software

There is some bugs with Title bar formatting.

If you put {Directory} to it and anything else it seems to ignore everything else than the directory. But it does not always ignore them. Sometimes shows but when you change folder or do anything in UI suddently everything else than directory disappears from title bar.

My objective is to get the directory more visible. I would want XnView MP text in the right very far from it. First I just tried to insert spaces but they didnt work. After that I tried dashes, didn't work either, underlines didnt work.

Optimal would be if you could align XnView MP text to right so it would be then as far away as your info as possible. But that is not a bug but a feature request and maybe more work to implement than fix those bugs so that you could move the text far away with spaces or dashes.

I would also want spaces to left side of directory between it and the logo.

Below you see what I would like to do optimally:

And here you see how it is now:

golemus wrote: Mon Jun 30, 2025 7:00 am If you put {Directory} to it and anything else it seems to ignore everything else than the directory. But it does not always ignore them. Sometimes shows but when you change folder or do anything in UI suddently everything else than directory disappears from title bar.

I can reproduce
any custom tag resets to {Directory} on folder change

golemus wrote: Mon Jun 30, 2025 7:00 am I would also want spaces to left side of directory between it and the logo.

put . in front of spaces

Whenever this is fixed it would be cool to have new formatting code something like {spacesonlyintitle}

{spacesonlyintitle[5]} would make 5 empty spaces that come to window title but do NOT come titles elsewhere like windows taskbar or task viewer. In taskbar the spaces are counterproductive and makes you see a title only with empty spaces.

Thanks to your detailed description I can reproduce the problem.

This problem is supposed to be fixed in XnView MP 1.9.3. Please check and confirm the bug fix here.

seems to be fixed