243 Production File Directory or Folder

<A HREF ="file:/projects/necatm/380/src/pnni">file:/projects/necatm/380/src/pnni</A>

OVw OpenView Motif This mail reports a reusable OpenView Windows selection dialog implementation. Selection in ovw depends on the Selection List, which can be accessed but not altered by an application. The application must take the list as it finds it. The code described is an example of such an interaction and can be substantially reused for any type of selection. The files involved are in ${PROJECT}/src/pnni/. They are as follows: The selection dialog itself: route/select/select.[hc] The X dialog box: xdialog/xdialog.[hc] X initialization, and message boxes: x/x.[hc] OVw initialization and map state checking: ov/ov-attach.[hc] OV return value checking utilities: ov/ov-utils.[hc] Execution tracing: util/tracing.[hc] (${PROJECT}/man/man1/tracing.1) Standardized memory allocation: util/myalloc.[hc] select.c needs to be tailored for the number and type of items being selected. It could also be altered to remove dependence on my utilities. The following is a guide to tailoring: In initSelect & selectEndsCb: set the callback action(s) to application defined menu item(s) to initiate the dialog. In selectDialogCb: set the number of items and the function called once the list is valid. In checkSelectList: check the list for validity. Various message strings and message processing functions would also need to be adapted. cheers Pushkar 20/11/97 pkp useful / does the job <A HREF ="mailto:pkp">mailto:pkp</A> CiTR/NEC 14/10/1997 NC380.6 library C SunOS