QCDHotKeys source code

[Paul]

This is probably considered by most an indispensible plugin for QCD. But it needs some TLC! For one, it needs Win key support.
Can you guys make it into everything that could be wanted?


Please post back modified project source back in this thread.

[Tokelil]

I dont think this is the right place to post requests to the Hotkey plug-in (for who ever takes it), a seperate thread should be made for that. (Or the forum searched.)
Never the less I would like to surgest that an API for other plug-ins to add global hotkeys is created. (Maybe through RegisterWindowMessage(_T("GlobalHotkeys"))?)
This brings plug-in dependency which is quite uncommon in QCD atm. but it would great IMO. But it's you call in the end Paul, so some indication about what you think about this would be good.

[Paul]

Making the HotKeys plugin take HotKey requests from other plugins? I don't have anything against that, although I'm not sure about the reason for it (other than being able to see all registered HotKeys in the same window, which I guess is legitimate). But it's easy enough for other plugins to register their own hotkeys.

It's my call as to whether I use the updates in QCD, but I encourage anyone to take the plugin in any directions they want.

[Rex_Mundi_Incarnit]

OKay, this is cool. Im no programmer so i'll just post the feature requests

Can we have hotkeys to restore and minimise qcd? Would these actions be controlled by the application itself? Afterall there is a hotkey to close qcd.

[teedoff087]

EDIT: Moved to feature request thread.

[Tokelil]

Lets keep this thread for development talk and post feature requests here:
http://www.quinnware.com/forum/showthread.php?p=37274

@teedoff087: A hotkey for the playlist isn't possible atm. because it depends on the skin used.

[Tropics]

at least i have downloaded it (and the other one too) ... if nobody else steps in i might be able to at least begin the work

[Tropics]

finally some news here ... i was able to get the WIN key working (took 2 days!). additionally there is the possibility of plugins registering their hotkeys.

paul: i need two message (maybe more later) ints which are currently unused and will stay unused. i don't want to use RegisterWindowsMessage to keep the interface as simple as possible. i was thinking about 41030 and 41031. any preferences?

[Paul]

What's the use-case for the new messages?

BTW: good job on the Win key. I knew it would be a PIA, which is why I prioritized it low.

[Tropics]

// send this msg to qcd/qmp
// note: you can't (shouldn't) send this msg in the entry point, as it
// might not have an effect then. the safe place to do this is in the
// Initialize function (that means for general plugins you need the
// QMP interface).
//
// WPARAM: the instance handle of your plugin
// LPARAM: a pointer to QCDInitHotkey struct
// returns 1 on success
#define QCD_CREATEHOTKEY 41030

// send this message to remove this plugin from the list
// WPARAM: the instance handle of your plugin
// return value 1: the plugin has been removed from the hotkey list
//              2: the plugin was not in the list because it didn't register callbacks 
#define QCD_REMOVEALLHOTKEYS 41031

thanks ... i had to write a whole new hotkey control for the win key to work correctly

[Paul]

Are you creating the plugin to respond to those two message? Or do you want QMP to respond to them, and in what fashion?

[Tropics]

ah no, the hotkeys plugin does the work. other plugins send those messages to the qmp window, and my plugin catches them and acts accordingly. its just that the messages need to be unused by qmp, as qmp would never get them.

[Paul]

Hey Tropics, how is this plug-in looking? I haven't personally used your updates yet but I would like to make them part of the official builds. Let me know how things stand.

Also, regarding the devoted message ID's - I think using RegisterWindowsMessage is actually a cleaner way to go as you just need to publish the message name the plug-in uses. It's the only way to guarantee it remains working in the future.

Thanks.

[Tropics]

The plugin is released and stable. Currently no update is planned. Would be nice to see it included in the release. The only problem i see is that i guess you want to have the source code and i feel like you when it comes to giving away source code of things that i made.

You are correct about the RegisterWindowsMessage stuff, and i am always using that functionality when it comes to internals. So far i think 41030 and 41031 are safe bets as the numbers that are used throughout QMP are nowhere near that range (all are < 41000). But i could change the behaviour in an update, of course.

[Paul]

Originally Posted by Tropics

The only problem i see is that i guess you want to have the source code and i feel like you when it comes to giving away source code of things that i made.

I almost understand, but you didn't make, you modified. I think this sets a bad precedent with regards to me releasing source to plug-ins.

I can't include plug-ins with the QMP installer that I can't vouch 100% for the contents of the source code.

[shaohao]

Hi, Tropics:
Is it possible for you make your HotKey open source? I want to help you improve the plug-in's UI.

[jklm105]

Ugg bootscheap ugg boots