Still a beta 2 problem (beta 3 just came in as I did this, EDIT: happens in beta 3 as well):
After converting, if I press ctrl+a in the conversion results window, it will highlight all tracks in the playlist underneath and not in the result window.
QUOTE(drake @ Nov 5 2007, 11:08) 
seems an easy enough question, but once i create a new UI element space (by putting in a splitter, whatever), how do i delete it?
Already explained earlier in this thread.
QUOTE(Borisz @ Nov 5 2007, 17:28)
After converting, if I press ctrl+a in the conversion results window, it will highlight all tracks in the playlist underneath and not in the result window.
Remove Ctrl+A from the keyboard shortcuts.
QUOTE(Frank Bicking @ Nov 5 2007, 18:33)
Remove Ctrl+A from the keyboard shortcuts.
Then it won't highlight at all. I use columns_ui, and the default core shortcuts just don't seem to work when another ui is used.
Assigning keys like Ctrl+A or Del globally worked and made sense as long as the interface was just a playlist.
But as of 0.9.5, controls are supposed to implement such basic keyboard shortcuts on their own.
In other words: it's not a problem of foobar2000, but of your custom UI.
But as of 0.9.5, controls are supposed to implement such basic keyboard shortcuts on their own.
In other words: it's not a problem of foobar2000, but of your custom UI.
QUOTE(Borisz @ Nov 5 2007, 11:30)
QUOTE(Frank Bicking @ Nov 5 2007, 18:33)
Remove Ctrl+A from the keyboard shortcuts.
Then it won't highlight at all. I use columns_ui, and the default core shortcuts just don't seem to work when another ui is used.
Try making Ctrl+A a non-global hotkey. That seems to work for me.
QUOTE(Frank Bicking @ Nov 5 2007, 19:39)
Assigning keys like Ctrl+A or Del globally worked and made sense as long as the interface was just a playlist.
But as of 0.9.5, controls are supposed to implement such basic keyboard shortcuts on their own.
In other words: it's not a problem of foobar2000, but of your custom UI.
Its still a problem that all the functions of the default ui shut down when another ui is active. Because of that I cant customize the search window, have to manually readd cut/copy/paste, cant use the spectrogram, and so on. Other uis are crosslinkable eg. I can still use the trackinfo field of panels_ui when I'm in columns (This may be the grand exception however, given the nature of the trackinfo panel).
Or, are these still accessible, just by different methods not yet supported by other uis? If so then indeed its a problem in columns_ui.
QUOTE(DocBeard @ Nov 5 2007, 20:15)
QUOTE(Borisz @ Nov 5 2007, 11:30)
QUOTE(Frank Bicking @ Nov 5 2007, 18:33)
Remove Ctrl+A from the keyboard shortcuts.
Then it won't highlight at all. I use columns_ui, and the default core shortcuts just don't seem to work when another ui is used.
Try making Ctrl+A a non-global hotkey. That seems to work for me.
It isnt a global hotkey in the first place. Global hotkey = works even when foobar is in the background, ex. to switch tracks while playing World of Warcraft without having to alttab out.
Aha. A little judicious testing confirms that Ctrl-A doesn't select everything in the converter window under Default UI *either*. So whatever the cause of this problem is, it's nothing to do with Columns UI.
(The reason I suggested using a non-global hotkey before is because Ctrl-A *does* work in other windows where you'd expect it to under columns/panels, such as the Track Info Display settings window).
(The reason I suggested using a non-global hotkey before is because Ctrl-A *does* work in other windows where you'd expect it to under columns/panels, such as the Track Info Display settings window).
QUOTE(DocBeard @ Nov 5 2007, 23:09)
A little judicious testing confirms that Ctrl-A doesn't select everything in the converter window under Default UI *either*.
Again, it works as long as you don't override Ctrl+A by assigning it to some other action at Preferences, Keyboard Shortcuts.
The "global" option has nothing to do with that - it makes shortcuts work from outside of foobar2000.
Ah, so it does, my apologies. So it's, what, a matter of the new way 0.9.5. handles keyboard commands breaking existing third-party components?
This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please click here.