Closed bk138 closed 1 year ago
outcome: they are still sent, altough #78 tried to prevent this.
SupportsClient2Server()
checks to shortcut certain functions to do nothingclient->supportedMessages
supportedMessages
is used on the libvncserver side to declare caps of the server and inform clients via SupportedMessages encodingDefaultSupportedMessages()
and add more if we encounter a Tight or Ultra server. The bad thing is these bitset settings happen after rfbGetClient()
and in fact after the first few messages are exchanged.supportedMessages
on the client if set initially get overridden by the lib :-/supportedMessages
are not only set by DefaultSupportedMessages()
but at least once also on receipt of certain messages (xvp being one case)supportedMessages
on the client are the only thing evaluated by the lib's functions to decide whether or not to do something :-/supportedMessages
actually the right place to save the lib user's intent? or is it rather just for managing state depending on the server?
cl.appData
info in libvncclient's functions directly and in addtion to supportedMessages
supportedMessages
from this all the time 😐supportedMessages
after rfbInitClient()
?
DefaultSupportedMessagesTight()
gets called later when a sectype is received, overwriting thisDefaultSupportedMessages()
call from DefaultSupportedMessagesTigh()
and ultra-counterpart?
DefaultSupportedMessages()
configurable via cl.appData
or the like?
cl.appData
for the init casesupportedMessages
re #125 #78