Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

LWin key press is not working #31

Closed
ex0dus-cpp opened this issue May 10, 2015 · 4 comments
Closed

LWin key press is not working #31

ex0dus-cpp opened this issue May 10, 2015 · 4 comments

Comments

@ex0dus-cpp
Copy link

I want to open Explorer on the remote machine, to which I joined by the rdpy.
To do this, i need to press the hotkeys win + e.
I do this with the following code:
self._controller.sendKeyEventScancode (347, True)
self._controller.sendKeyEventScancode (18, True)
self._controller.sendKeyEventScancode (18, False)
self._controller.sendKeyEventScancode (347, False)
Since the keys scancode lwin = 347.
But the key is not pressed.
Can you please tell me what code i should write to do this.

@citronneur
Copy link
Owner

Hi,

I fixed some bugs which block lwin keys. Can you try the last commit on hotfix branch with this code:
self._controller.sendKeyEventScancode (91, True, True)
self._controller.sendKeyEventScancode (18, True)
self._controller.sendKeyEventScancode (91, False, True)
self._controller.sendKeyEventScancode (18, False)

(i use proxy to determine lwin scancode => 91)

I test with a timer from onready event because your session need to be started before and there is no event that signal session state. This work well for me. An alternative is to use lanch application parameter of controller but this doesn't work well on all station.

Best regards,
Sylvain.

@citronneur
Copy link
Owner

I found a way to know when you can send command. There is a new event onSessionReady over RDPClientObserver. You can use code on last message on this event. This work very well for me... Now we can do a lot of things...

I'm waiting to close another bug and release new hotfix at the end of the week.

Sylvain.

@citronneur
Copy link
Owner

Close issue when release will be ready.

@citronneur
Copy link
Owner

Fix on 1.3.2

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants