Open topic with navigation
WTSupported in traditional Synergy on Windows
WNSupported in Synergy .NET on Windows
USupported on UNIX
VSupported on OpenVMS
subroutine C_METHNOP, reentrant in req container_id ,n in req type ,n in req child_id ,n in req reason ,a opt record ,a opt a_methoddata1 ,any . . . opt a_methoddata20 ,any
This argument is not used by the default processing methods. However, it passes the ID of the container window in case a method you supply needs this information. (n)
This argument is not used by the default processing methods. However, it passes one of the following (defined in tools.def) in case a method you supply needs this information: DC_LIST for a standard Toolkit list or an ActiveX Toolkit list, or DC_WINDOW for a Toolkit window. (n)
This argument is not used by the default implementation of C_METHNOP. However it passes the ID for the child for other methods that need this information. (n)
The reason the child was activated, which can be blank (indicating the child was already activated), a program‑supplied reason passed because the child was activated programmatically, or one of the following: (a)
C_FIRST = Focus moved in attempt to reach first child.
C_LAST = Focus moved in attempt to reach last child.
C_NEXT = Focus moved from previous child (e.g., tab).
C_PREV = Focus moved from next child (e.g., shift+tab).
C_SET = Child explicitly activated. For example, this could be the result of a mouse click, or it could be that the child was activated programmatically without a specified reason.
(optional) This argument is not used by the default method C_METHNOP. However, this argument passes a copy of the a_methoddata argument specified by recordindex (a DC_ADD argument) for other methods that need this information. (a)
a_methoddata1 through a_methoddata20
(optional) These arguments are not used by the default method C_METHNOP. However, up to 20 additional data arguments are passed for other methods that need this information. (any)
C_METHNOP is a Toolkit‑supplied processing method that C_PROCESS calls by default when processing a child window that doesn’t fit into one of the general classifications that invoke other default processing methods (see the C_PROCESS Discussion) and for which no method was assigned when it was added to the composite window. For example, this method will be used for a child window created with .WINDOW, assuming no method was assigned in its DC_ADD call and assuming that T_SETUP has not been called for it (which would cause C_PROCESS to use C_METHTXT).
If you want something other than the default processing for such windows—which is simply to skip over the window (C_METHNOP calls %M_SIGNAL with “C_PREV” or “C_NEXT”)—you can instruct C_PROCESS to call a different routine when processing the window by passing the routine’s name in the DC_ADD call for the window. Additionally, you can assign this method to any child window or list that you don’t want to be activated.
To see the code for this method, see the ctrmeths.dbl file included in your UI Toolkit distribution. This file is distributed simply as a reference and a starting point for writing your own composite window processing methods; modifying or compiling this file will not change the default methods.