smw/deskflow
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

docs: fix missing refs warnings

Browse source 
EXTRACT_STATIC
flag 2 private methods
This commit is contained in:
laz-001 2025-06-26 15:19:28 +03:00 committed by Nick Bolton
parent 22b1e8e543
commit f784705a7e
2 changed files with 3 additions and 2 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

1
doc/CMakeLists.txt
View file

@ -8,6 +8,7 @@ option(BUILD_DEV_DOCS "Build and install developer documentation" OFF)
if (DOXYGEN_FOUND) if (DOXYGEN_FOUND)
# Generic Doxygen options # Generic Doxygen options
set(DOXYGEN_EXTRACT_ALL YES) set(DOXYGEN_EXTRACT_ALL YES)
set(DOXYGEN_EXTRACT_STATIC YES)
set(DOXYGEN_STRIP_FROM_PATH ${CMAKE_SOURCE_DIR}) set(DOXYGEN_STRIP_FROM_PATH ${CMAKE_SOURCE_DIR})
set(DOXYGEN_QUIET YES) set(DOXYGEN_QUIET YES)
set(DOXYGEN_PROJECT_NAME ${CMAKE_PROJECT_PROPER_NAME}) set(DOXYGEN_PROJECT_NAME ${CMAKE_PROJECT_PROPER_NAME})

4
doc/dev/protocol_reference.md
View file

@ -228,7 +228,7 @@ When encryption is enabled, the protocol follows this sequence:
3. Protocol handshake begins only after TLS session is established 3. Protocol handshake begins only after TLS session is established
- **Implementation Details**: - **Implementation Details**:
- The client initiates a standard TCP connection, then the @ref SecureSocket::handleTCPConnected method is called, which begins the TLS handshake - The client initiates a standard TCP connection, then the (private) SecureSocket::handleTCPConnected method is called, which begins the TLS handshake
- **Certificate Validation**: - **Certificate Validation**:
- Client implementations **must** validate the server's certificate - Client implementations **must** validate the server's certificate
@ -260,7 +260,7 @@ A modifier (modifier mask) represents the state of modifier keys (like Shift, Co
- Upon receiving a kMsgCKeepAlive message, the client must immediately send a kMsgCKeepAlive message back - Upon receiving a kMsgCKeepAlive message, the client must immediately send a kMsgCKeepAlive message back
- The client maintains a timeout that is reset each time any message is received - The client maintains a timeout that is reset each time any message is received
- If no message is received for 9.0 seconds (3 × @ref kKeepAliveRate), client must disconnect - If no message is received for 9.0 seconds (3 × @ref kKeepAliveRate), client must disconnect
- This is handled by the @ref ServerProxy::handleKeepAliveAlarm method - This is handled by the (private) ServerProxy::handleKeepAliveAlarm method
<a id="constraint-screen-entry-sync"></a> <a id="constraint-screen-entry-sync"></a>
### Synchronization on Screen Entry ### Synchronization on Screen Entry