akallabeth

@D-Y-V well, if you tell me which one is not fixed I repoen ;)

@D-Y-V ok, so you mean the same as before? Just wanted to be sure, as you said ` Not all fixed. Some err still exists.`

@hardening looks like your guess is right. this looks exactly as if the pointer hotspot is not properly added/removed after clicking.

@vscfreire when does that happen? (with current freerdp builds or something custom?) the flags have been fixed on master, so the next backport is most likely to have this.

@vscfreire backport won´t happen as it breaks the stable API. (windows is not a major target for 2.0, `wfreerdp` is lacking a maintainer)

hard to tell if we know nothing about your setup ;)

@JSSSSSSSSSS Ok. then you have the following possible problems: 1. Do you use the correct destination to connect (IP might not be a proper realm/domain) 2. Do you use the...

@JSSSSSSSSSS thank you. and well, no, there are none as kerberos support is still not stable (you might have seen that `option(WITH_GSSAPI "Compile support for kerberos authentication. (EXPERIMENTAL)" OFF)` defaults...

@reddwarf666 copy in one direction (client -> server) is already supported by `xfreerdp` (#3905). For the other direction some work is necessary. pull requests welcome.

@reddwarf666 ah, ok. could get challenging as some kind of async file data request is necessary (on linux it may be possible to use fuse) but mac could get challenging....