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: foobar2000 for Mac: bugs (Read 23095 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

Re: foobar2000 for Mac: bugs

Reply #50
New "Edit Layout …" item also has an unnecessary space before the ellipsis.

Re: foobar2000 for Mac: bugs

Reply #51
I agree that it should be consistent, but the space isn't a bug -- just look at the menu of apple's mail app. I also think it looks better with a space before the ellipsis (though that's subjective).

Re: foobar2000 for Mac: bugs

Reply #52
I have a bug to report.

Consider the following layout:
Code: [Select]
splitter horizontal style=thin
 splitter horizontal style=thin
  splitter vertical style=thin
   playlist-picker
   playlist
  tabs position=top
   refacets tab-name="A"
   refacets tab-name="B"
 playback-controls
Now if foobar2000 is opened, and I tweak refacets A and B, add different filters and so on everything is fine. Once I close foobar2000, refacets A = refacets B This means that all the filters that are in A, are also in B. I think it picks the refacet it was last modified as the context of the change.

Tested on the latest Macos preview version v2.7 07-07-2024

Re: foobar2000 for Mac: bugs

Reply #53
I agree that it should be consistent, but the space isn't a bug -- just look at the menu of apple's mail app. I also think it looks better with a space before the ellipsis (though that's subjective).

Looked through all the menus of Apple Mail. Spaces are nowhere to be seen. And foobar2000 itself doesn't have them in most cases, I only pointed out three exceptions that are probaly just errors.



Re: foobar2000 for Mac: bugs

Reply #56
Bug: v2.7 2024-07-08 crashes when selecting any of the options from File Operations (Library element) other than Delete files

Files stored on NAS. Don't think this happened on the previous preview version

Re: foobar2000 for Mac: bugs

Reply #57
Thanks for the bug report.

File Operations crash should be fixed in today's build.
Microsoft Windows: We can't script here, this is bat country.

Re: foobar2000 for Mac: bugs

Reply #58
foobar2000 still uses proportional figures when showing elapsed/remaining time and because of that they jiggle slightly now and then (which is not good, imo).

Re: foobar2000 for Mac: bugs

Reply #59
I found a bug in v2.7 2024-09-11 but i think I encountered this bug in older versions too. Playlist Search won’t open again after double clicking a file in the search window.

Steps to reproduce:
  • Open Playlist Search
  • Type search term
  • Double click a result
  • Close Playlist Search
  • Try to open Playlist Search again

Also, is there a keyboard shortcut for the playlist or library search?
According to the Apples guidelines it should be Option-Command-F but a lot of apps also use Option-F as the search shortcut. Even official apps from Apple like Music, Mail, Calendar, Contacts,... use Command-F for searching.
https://developer.apple.com/design/human-interface-guidelines/keyboards

 

Re: foobar2000 for Mac: bugs

Reply #60
I noticed this behaviour: if I filter in the album list the tree is correctly filtered according to the query. In the screenshot four tracks have been selected by the filter. I now would expect that double-clicking on "All Music (4)" would only transfer the tracks selected by the filter to the playlist. But what happens is that in addition all other tracks in the library are transferred to the playlist.

Sorry for bumping my own post, but is this a bug or normal behaviour?

Re: foobar2000 for Mac: bugs

Reply #61
Thanks for the bug reports.

New build is in the making, issues from last 3 posts have been addressed.

Keyboard shortcuts are still a work-in-progress subject, I'll look into it later.
Microsoft Windows: We can't script here, this is bat country.