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

FreeRDP clipboard MonitorReady event #3331

Closed
sergsalo opened this issue May 11, 2016 · 5 comments
Closed

FreeRDP clipboard MonitorReady event #3331

sergsalo opened this issue May 11, 2016 · 5 comments

Comments

@sergsalo
Copy link

it seems to me that in FreeRDP v2.0xx event MonitorReady is not sent anymore. We used this event as an indicator that clipboard is ready to be used. Client and Server are both windows 2012 r2 hosts.

@byteboon
Copy link
Contributor

byteboon commented May 11, 2016

We are using 2.0xx code and do receive the MonitorReady call.

We have a PubSub_SubscribeChannelConnected hook that watches for the channel name of CLIPRDR_SVC_CHANNEL_NAME and initializes the cliprdr context callbacks (including MonitorReady). After that, we get the event fine --- so I know it can work.

Is this something you had working previously?

@sergsalo
Copy link
Author

seems like that's exactly what we do.
yes, it worked with 1.xx
Good to know it works, so I'll keep digging

@sergsalo
Copy link
Author

@byteboon what version of FreeRDP are you using? maybe i can try build that one and see if there is any difference.

@byteboon
Copy link
Contributor

We're using an older version of 2.0 with patches in production, but I was able to test with master as of yesterday and it was still working.

@spimenov
Copy link

spimenov commented Jun 3, 2016

We run into similar problem with the new FreeRDP version. MonitorReady was not sent and clipboard didn't work. Problem was in our ServerCapabilities function that returned 1. It looks like old FreeRDP version ignored the return value and our code worked fine. Now FreeRDP checks the returned values and MonitrReady was not sent after that. The fix was simple - ServerCapabilities returns 0. As all other callback functions.

@sergsalo sergsalo closed this as completed Jun 3, 2016
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

3 participants