kyriakos876 wrote:Is this Bug known?
This hasn't came up before (as far as I know), but I am not it qualifies as a bug. Let me explain.
The plugin works by setting a 'global keyboard hook' on the Windows system. Since many programs (and the Windows system itself) need/can react to keystrokes regardless of which window has the keyboard focus, there is something called a hook chain that basically passes whatever key was pressed to each program one at a time. Of course the Windows system gets it first (for things like CTRL+ALT+DEL, and others). It then passes the keystroke to the next hook in the hook chain (usually its starts with the hook that is 'newest'). This happens before the window with keyboard focus actually gets the keystroke.
'Good' programs that use keyboard hooks are supposed to pass it along to the next hook. However, the hook chain can be broken easily by not calling the next hook.
Microsoft MSDN link (in the Remarks sections): https://msdn.microsoft.com/en-us/library/windows/desktop/ms644990(v=vs.85).aspx
Microsoft wrote:Calling the CallNextHookEx function to chain to the next hook procedure is optional, but it is highly recommended; otherwise, other applications that have installed hooks will not receive hook notifications and may behave incorrectly as a result. You should call CallNextHookEx unless you absolutely need to prevent the notification from being seen by other applications.
The plugin correctly calls the next hook here: https://github.com/brianferguson/HotKey.dll/blob/master/PluginHotKey/PluginHotKey.cpp#L413
So, I suspect that the LG software is installing a global hook to capture some keystroke (for whatever reason, probably navigation of folders, or maybe for some search function), however it is not correctly passing the key stroke to the next hook in the chain. This is my best guess.
kyriakos876 wrote:what should I do to resolve this?
To remedy this you could try delaying Rainmeter from starting before your LG Smart Share software. Or you could just manually start Rainmeter after you know the LG software has started. Or you could delay the loading of your specific skin by making another skin that will wait for specified amount of time before activating the skin that uses the HotKey plugin. Basically we want Rainmeter (or the skin that uses this plugin) to be the 'newest' in the hook chain to get first dibs on the keystroke.
I am curious to know if there was any error messages in the log when this happens? You may need to activate logging since the error might happen before the About dialog is initialized. https://docs.rainmeter.net/manual/user-interface/manage/#Logging