will add it in for the next release (whenever that happens). i had the jtf window in manage mode instead of search mode at the time and forgot it's not there for the search mode handling.
#1: not viable since it'd break most of the listviews functionality (plus would be a nightmare to implement). as such the send to menu is the safest and easiest way to implement such functionality. however i have possibly thought of implementing the ml_enqplay plugin into jtfe (which would allow me to possibly insert a menu item in place to do what's needed but that plugin isn't complete yet so i won't be looking into that for a while)
#2: look at the shell options page in the preferences for that functionality
#3: not quite sure how jtfe would be responsible for that since the plugin will try to use the appropriate apis where possible for passing a title with any files (unless you've got reading of playlist titles off until they're played or something like that)
-daz
I was wondering if there has been any progress on adding a hotkey to do the same action as right-click>send to:> add to queue from media library - in my opinion the queue functionality in itself sets Winamp apart from every other media player but I'd rather not drag files to the playlist and queue with the middle-mouse button or "q" key if I could just use a hotkey from the ML... I understand this may not be a simple task to complete but it's been 5 years so I figured I'd ask The other reason why I ask is because I'm working on modifying someone else's touchscreen skin and can't drag and drop to the playlist - perhaps someone knows of a way to replicate a menu path just like you can replicate hotkeys (CreateObject("WScript.Shell").SendKeys "^%q" to let the click of a button replicate Alt+Ctrl+Q).
i've not done anything towards it since as per what was quoted, it's not viable since there's no way from a hotkey to query the selection within a library view (if it's even set to that) to then be able to queue up those items.
even if it gets added to the ml_enqplay plug-in, adding a global hotkey wouldn't really work since it comes back to the same issue as trying to do it with this plug-in.
not sure where you're getting the 5 years thing from since you've only been registered for 2
Thanks for the quick response. I just searched through the thread and didn't find much about this topic since 2006 (the quoted post), figured someone might have worked on the functionality since then.
i suppose it could be done by hacking into the library views at a low level, but that's just not something i've time / inclination to do and would be too version specific so would probably cause me more issues than it'd be worth it (assuming it'd work to start with).
but doing it properly without hacking things, etc then there is no way to do it and i'm not expecting anything like that to happen in the next 5 years to come, heh.
Added IPC_GET_JTFE_QUEUE_UPDATE to notify when there are changes made to the queue contents (details will follow in updated sdk)
Added checks on start-up to attempt a refresh of the icon pack (if one is specified) after a Winamp update
Added 'shift' handler to up / down queue management buttons to change them into a move to top / button respectively
Added view file info (alt+3) option to the main jtf window right-click menu (now matches with the management views)
Changed queue management buttons to be disabled when there are no appropriate actions available e.g. empty queue
Fixed handling of adding of urls to the queue when using drag and drop from the library
Fixed jtf window not selecting the current song if the first search result on opening in some situations
Fixed the [<<][>>] buttons on the alt+3 dialog appearing when they should not be in some situations
Fixed the skinned jtf and queue manager windows not appearing correctly at times (should resolve jtf window not appearing always)
Fixed possible crash when dragging files onto the queue if there was no length obtained from the file
Fixed queue position not showing in the playlist editor (v1.2.4 issue)
Fixed crash on loading when queue position not showing in the playlist editor (v1.2.4 issue)
Fixed 'shift' handler for up / down queue management buttons not working in the queue manager window (v1.2.4 issue)
Currently this is only available in the 5.622 release and will sort out a separate installer + sdk installer update during the next few days. Also i've not changed over building of the plug-in with VS2008 (like the rest of Winamp) instead of MSVC6, so the current compile will only work on 5.57x and up - debating if i keep support as this or not...
[edit - 5th Nov 2011]
Have updated changelog and merged the v1.2.4 changes in with v1.2.5 which is now available for separate download.
"Display Use text formatting in the playlist: Determines how to display the text and queue position number for queued items in the Playlist Editor window."
Until this new version it worked fine. Now, when you click middle mouse button in PL there is no number (que), but only background color is changed (if enabled). I'm using this option a lot and I really miss it. HELP
ok, i think i've found the cause of the issue with the queue position not working - another fallout from the change in the compiler used to build the plug-in. will post an updated version once i'm certain there's nothing else at fault with the plug-in, etc.
O.K. It's working again. Thank you for such a quick reply. And that's why forums like this exist and, also, that's why WinAmp is still the best.
AVE DrO!
first thing, you're using the first instead of second 5.622 release (build 3188 instead of build 3189). so would suggest you re-download the Winamp installer and then install the newer JTFE version from http://forums.winamp.com/showthread....32#post2813132
if that doesn't resolve things, then from your list the following are ones that i'm not sure about and might be causing it to not work (something i cannot replicate):
you can try by renaming them from .dll to .off and see if it still happens. if it doesn't then you'll need to rename one back to .dll and try again to determine which one causes the issue and see if there is an updated version of the plug-in available (or try to contact the plug-in author).
Comment