Skip to main content ↑ ↓

Notice

Please note that most of the software linked on this forum is likely to be safe to use. If you are unsure, feel free to ask in the relevant topics, or send a private message to an administrator or moderator. To help curb the problems of false positives, or in the event that you do find actual malware, you can contribute through the article linked here.
Topic: foobar2k window title behaviour under WIN11 (Read 834 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

foobar2k window title behaviour under WIN11

Hi.

Title behavior worked fine in Windows 10. After switching to Windows 11, it no longer works quite properly.

I can't insert any spaces before the title in the Foobar2K window. The functions $pad_right and/or $repeat($char(32),50) for inserting blank characters does not work either.

Interestingly, it is OK in the preview in the Foobar2K configuration. Only the window title itself does not work in Windows 11 for Foobar2K.

See the screenshot:
X

Apparently there will be some problem with access to windows in Windows 11 system.

Does this work correctly for anyone ? Can someone test it for me ?

Thanks.

OS: Windows 11 - 22H2 - 22621.3007
Foobar2K: 2.1 x86

Re: foobar2k window title behaviour under WIN11

Reply #2 –
Hi. Thanks for the quick reply.

This $tab() doesn't work either.

It looks like attempts at blank characters are ignored - but only at the left side in the window title.

BTW, on the right side (as you may have noticed) I use whitespace as well, but only for the purpose of moving the name and version of "Foobar vX.X" somewhere "into the void". So, that it is not visible in the window title :) .
 

Re: foobar2k window title behaviour under WIN11

Reply #4 –
Yep... exactly !

I inserted some character (a dot, specifically, as in your case). And the following blank characters after the dot have already been displayed.

It can also be seen that the padding function also works correctly in the window title:
X

Thanks for testing and confirming. So it's some kind of compatibility problem with Windows 11.