Hello,
documentation does not mention TRANSPORT_PROTOCOL. What is the meaning of TRANSPORT_PROTOCOL in configuration file (.scg)? What is the difference between NO_TRANSPORT, MWM_TRANSPORT, PXY_TRANSPORT, S80_TRANSPORT and WIN32_KEYBOARD?
Thank you in advance.
Best regards
striso
TRANSPORT_PROTOCOL
Moderator: Moderators
Hi striso,
Many things are not documented in the .scg files <G>
TRANSPORT_PROTOCOL is a hint to the driver of how an application is planning on communicating with the driver.
NO_TRANSPORT means nothing in particular is specified. Either MWM or S80 will be handled.
MWM_TRANSPORT indicates that the application will use an old Windows messaging protocol that is only used by a few applications.
S80_TRANSPORT indicates that the application is using the 3Dx C/C++ SDK mechanism.
PXY_TRANSPORT indicates that the application uses a Proxy DLL (UdPxy directory DLL -- a callback mechanism used by 3DxOffice).
WIN32_KEYBOARD is the only one that absolutely needs to be specified. It indicates that this application is only supported by throwing keyboard macros at it. All the other protocols will register with the driver to indicate that they are interested in receiving events. WIN32_KEYBOARD applications are "write only". They never contact the driver. It is up to the driver to notice that they are in focus and start sending keyboard events to them.
Many things are not documented in the .scg files <G>
TRANSPORT_PROTOCOL is a hint to the driver of how an application is planning on communicating with the driver.
NO_TRANSPORT means nothing in particular is specified. Either MWM or S80 will be handled.
MWM_TRANSPORT indicates that the application will use an old Windows messaging protocol that is only used by a few applications.
S80_TRANSPORT indicates that the application is using the 3Dx C/C++ SDK mechanism.
PXY_TRANSPORT indicates that the application uses a Proxy DLL (UdPxy directory DLL -- a callback mechanism used by 3DxOffice).
WIN32_KEYBOARD is the only one that absolutely needs to be specified. It indicates that this application is only supported by throwing keyboard macros at it. All the other protocols will register with the driver to indicate that they are interested in receiving events. WIN32_KEYBOARD applications are "write only". They never contact the driver. It is up to the driver to notice that they are in focus and start sending keyboard events to them.