[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference bulova::decw_jan-89_to_nov-90

Title:DECWINDOWS 26-JAN-89 to 29-NOV-90
Notice:See 1639.0 for VMS V5.3 kit; 2043.0 for 5.4 IFT kit
Moderator:STAR::VATNE
Created:Mon Oct 30 1989
Last Modified:Mon Dec 31 1990
Last Successful Update:Fri Jun 06 1997
Number of topics:3726
Total number of notes:19516

2357.0. "Are changes like this documented somewhere?" by SMAUG::DESMOND () Mon Feb 26 1990 14:41

    I noticed when updating to VMS 5.3 that our DECwindows 3270 Terminal
    Emulator will no longer link.  There is an unresolved external routine
    called DwtDrmRCValid which turns out to be a macro that is now called
    XmDrmRCValid.  Why has this changed and are there a lot of changes to
    the names of other routines or macros?  Can I be assured that it will
    remain with the current name?  I'd like to update our source code here
    but I want to make sure this is permanent and I couldn't find anything
    about it in the release notes.
T.RTitleUserPersonal
Name
DateLines
2357.1GOSOX::RYANDECwindows MailTue Feb 27 1990 08:137
	It hasn't changed for VMS V5.3 - the Xm prefix refers to a Motif
	routine. It sounds like someone installed Motif on your system
	in such a way that it's interfering with the normal DECwindows
	environment (system-wide definition of C$INCLUDE to point at
	Motif directories?).

	Mike
2357.2SMAUG::DESMONDTue Feb 27 1990 11:107
    I checked the DECwindows DECW$INCLUDE directory on my workstation and
    it also has the routine named XmDrmRCValid in DRMPUBLIC.H.  I installed
    DECWindows from a CD containing all VMS 5.3 files and I did not installed
    Motif.  Were some Motif files included in the DECWindows kit for VMS
    5.3 by mistake or design?
    
    						John
2357.3Toolkit V5.3 and Motif V1.0 share some common codeLEOVAX::TREGGIARITue Feb 27 1990 12:416
In the areas that we did work for Motif V1.0 (specifically, UIL, DRM, and
compound strings).  However, I don't know why "Xm" names show up in
*public* .h files, and they certainly shouldn't have changed the name of 
something in a public .h file.

Leo
2357.4SMAUG::DESMONDTue Feb 27 1990 15:133
    Is there someone I should officially point this out to?  The .h files I
    have came off of the VMS AD Software Consolidation CDs so I assume this
    is the same as the kits that are sent to customers.
2357.5QAR itLEOVAX::TREGGIARITue Feb 27 1990 15:381
Leo
2357.6Not in my copy, it's notR2ME2::VANGILDERJim V., DECwindows ToolkitsSun Mar 04 1990 13:0517
I just checked our copy of DrmPublic.h (which should be the official 5.3
version).  The only reference to *RCValid* that I find is:

/*
 * Validation macro, returns TRUE/FALSE
 */
#define	UrmRCValid(context) ((context)->validation==DRMResourceContextValid)


And no references to Xm* anything.  And in any case, XmDrmRCValid isn't the
right name even for the Motif kit (it's still UrmRCValid).

Mail me your copy of DrmPublic.h so I can take a look at it.

    Jim

2357.7oops, they ARE in thereR2ME2::VANGILDERJim V., DECwindows ToolkitsMon Mar 05 1990 09:105
    Oops - I must have been looking in the wrong directory.  DRMDECLS.H
    and DRMPUBLIC.H do indeed have Xm* routines declared.  As Leo said,
    QAR it.