MrmRegisterNamesInHierarchy man page on OSF1

Man page or keyword search:  
man Server   12896 pages
apropos Keyword Search (all sections)
Output format
OSF1 logo
[printable version]

MrmRegisterNamesInHierarchy(3X)		       MrmRegisterNamesInHierarchy(3X)

NAME
       MrmRegisterNamesInHierarchy  - Registers the values associated with the
       names referenced in UIL within a single	hierarchy  (for	 example,  UIL
       callback function names or UIL identifier names)

SYNOPSIS
       #include <Mrm/MrmPublic.h>

       Cardinal	 MrmRegisterNamesInHierarchy(hierarchy_id, register_list, reg‐
       ister_count)
	       MrmHierarchy hierarchy_id;
	       MrmRegisterArglist register_list;
	       MrmCount register_count;

DESCRIPTION
       The MrmRegisterNamesInHierarchy function registers a  vector  of	 names
       and  associated	values	for  access in MRM. The values can be callback
       functions, pointers to user-defined data,  or  any  other  values.  The
       information  provided  is used to resolve symbolic references occurring
       in UID files to their run-time values.For callbacks,  this  information
       provides	 the  procedure	 address  required  by the Motif Toolkit.  For
       names used as identifiers in UIL, this information  provides  any  run-
       time mapping the application needs.

       This  function is similar to MrmRegisterNames, except that the scope of
       the names registered by MrmRegisterNamesInHierarchy is limited  to  the
       hierarchy  specified  by	 hierarchy_id, whereas the names registered by
       MrmRegisterNames have global scope. When MRM looks up a name, it	 first
       tries  to find the name among those registered for the given hierarchy.
       If that lookup fails, it tries to find the name among those  registered
       globally.  Specifies the hierarchy with which the names are to be asso‐
       ciated.	Specifies a list of name/value pairs for the names to be  reg‐
       istered.	  Each name is a case-sensitive, NULL-terminated ASCII string.
       Each value is a 32-bit quantity, interpreted as a procedure address  if
       the  name  is a callback function, and uninterpreted otherwise.	Speci‐
       fies the number of entries in register_list.

       The names in the list  are  case-sensitive.  The	 list  can  be	either
       ordered or unordered.

       Callback	 functions  registered through MrmRegisterNamesInHierarchy can
       be either regular or creation callbacks. Regular callbacks have	decla‐
       rations	determined  by	Motif  Toolkit and user requirements. Creation
       callbacks have the same format as any other callback:

       void CallBackProc(widget_id, tag, callback_data)
	       Widget *widget_id;
	       Opaque tag;
	       XmAnyCallbackStruct *callback_data;

       Specifies the widget ID associated with the widget performing the call‐
       back (as in any callback function).  Specifies the tag value (as in any
       callback function).  Specifies a widget-specific data  structure.  This
       data structure has a minimum of two members: event and reason. The rea‐
       son member is always set to MrmCR_CREATE.

       Note that the widget name and parent  are  available  from  the	widget
       record accessible through widget_id.

RETURN VALUE
       This  function  returns one of these status return constants: The func‐
       tion executed successfully.  The function failed.

					       MrmRegisterNamesInHierarchy(3X)
[top]
                             _         _         _ 
                            | |       | |       | |     
                            | |       | |       | |     
                         __ | | __ __ | | __ __ | | __  
                         \ \| |/ / \ \| |/ / \ \| |/ /  
                          \ \ / /   \ \ / /   \ \ / /   
                           \   /     \   /     \   /    
                            \_/       \_/       \_/ 
More information is available in HTML format for server OSF1

List of man pages available for OSF1

Copyright (c) for man pages and the logo by the respective OS vendor.

For those who want to learn more, the polarhome community provides shell access and support.

[legal] [privacy] [GNU] [policy] [cookies] [netiquette] [sponsors] [FAQ]
Tweet
Polarhome, production since 1999.
Member of Polarhome portal.
Based on Fawad Halim's script.
....................................................................
Vote for polarhome
Free Shell Accounts :: the biggest list on the net