Conference bulova::decw_jan-89_to_nov-90

When you ran the old FileView on your V3 server, were you using your 
yoru V3 profile?  Have you customized fileview with V3 before using it
with V2? Does this happen with all menus, or with one?  Which one?

This is the expected result of the "fix" they put into the VMS DECwindows V3
server.  The server now checks unused bits in the DoNotPropagate mask for
zero.  It used to ignore them.  What this means is that the old FileView
menu widget now generates illegal parameter errors on the new server,
since it sets all the bits in the DoNotPropagate mask rather than just
setting the defined ones.

Before you flame at me too much, please consider that this was a perfectly
valid thing to do and there was good logic for why a widget should be
written that way.

This reflects an incompatible change made to the MIT server.  I had a futile
discussion with the VMS/DECwindows group trying to convince them that they
should maintain the server such that it remains compatible with old clients
(continue to ignore unused bits).

In other words, if you submit an SPR, I think it should go to the server group.
There was one other client application (PAINT?) that was impacted by this
change, but I don't remember the details.  So FileView is not the only culprit.

-steve-

There are patches to both Paint and FileView that fix the problem
Steve mentions.  (These fixes were needed so that Paint and FileView
could be used with other vendor's servers that adhere to the MIT R4
convention.)  I don't know if these patches will fix your problem.

Sorry, I don't know specifically where you can get these patches.

Thanks for yor explanations.
However, I feel that these patches should be made available to everybody. It is
a common environment where you have newer versions of software living together
with the older versions ! As we claim to be upward compatible, they should be
able to coexist. Our development environment is setup such that we have a big
cluster running the latest released versions of layered products and VAXstations
running field test versions. This way we can gain the advantage of the different
versions of layered products. If we want to have access to DECwindows V2 from
a V3 server, I think this should be perfectly possible without limitations such
as not being able to use a great tool like Fileview.

So, please tell us where we can get the fix for Fileview V2 to work on a
DECwindows V3 server !

Thanks.

If I understand this correctly, I will not be able to use FileView running on
a "standard" VMS V5.3 system with the display on my workstation if I move to 
DECwindows V3.  Is this correct?

If so, I may not be able to participate in the field test.  My memory-poor
workstation can't run everything locally.  I use FileView regularly running
on a 6220 with the display set back to my workstation.

I also see MAJOR repercussions for our customers if this isn't changed.  You'd
be forcing all systems to coordinate upgrades.  Nasty.

	- Dave

As I recall, the problem was identified last winter or spring.  There have been
two releases of VMS since then, so I hope this patch is already in V5.3-2 and
V5.4; can someone confirm that this is the case, or does this need to go into
V5.4-1.  If no one knows for sure, I'll post this note as a showstopper qar for
v541-ft tonight.

Contact your CSC for this patch.  I don't believe there is a patch for VMS 5.4
(yet)...  The patch is not in 5.3.  I have not tested 5.4. Has anybody?

Jeff

Ahhh...the problem is *not* with DECwindows V3?  I did not understand.

If there is a patch for DECwindows V2 FileView and Paint to fix this, I can
certainly find it.  I thought it was a SERVER side problem!

	- Dave

Date:	 9-NOV-1990 13:44:27.47
From:	STAR::VATNE       
Subj:	RE: FIleView - X Server incompatibility
To:	CVG::PETTENGILL
CC:	STAR::VATNE,LOWELL::KLEIN,DECWIN::JACKIE
9 records
Attributes: Replied, Deleted
The fix for FileView was made on 23-Mar-1990 (file VMENU.C, generation 12).
This was definitely fixed for VMS V5.4 in source form.

I remember helping Kathryn Begley create a patch command file for
a dash release, but I don't remember off the top of my head which
release it went in.  I also don't remember if it was given to the
CSC's to be made into a distributable patch.

Peter

Date:	 9-NOV-1990 13:50:51.06
From:	STAR::VATNE       
Subj:	RE: FIleView - X Server incompatibility
To:	CVG::PETTENGILL
CC:	STAR::VATNE,LOWELL::KLEIN,DECWIN::JACKIE
4 records
Attributes: None
I just checked the contents of VMS V5.3-2, and it does not appear that
the patch is in that release. 

Peter

I just remembered: the other offending application was Calendar,
not Paint.

Both of these problems were found at Connectathon-90 in San Mateo,
where we tested our applications and server against all the other
vendor's applications and server.  The main incompatibilities
were in the area of fonts, and the problem with FileView and
Calendar.  (There were also some minor byte-swapping problems
in DECwrite.)

As you can see, we fixed the FileView problem in V5.4 which means
that no patch is required for that release.  It also means that
the problem is fixed in DECwindows V3.  And we did submit the
patch to CSSE (thanks, Jeff, for the patch info!)

The font fallback problems will all be corrected in V3.  In the
meantime, there is a font alias file workaround (see note 2509).

I can confirm that FileView in 5.3-2 has this problem and that it is OK
in 5.4-0A.  I imagine that plain ole 5.4 is ok, too.

To clear my mind - what do I need to make v2 vue display / work ok on v3. 
and where can I get it?

Thanks
Paul H.

I have installed the patch on our V5.3-2 system and now I am able to use a
V2 fileview under a V3 server. The installation of the patch only patches
VUE$MASTER and takes only two minutes.

Yep, the patch seems to work ok.

If you have no other resource for the patch, I can mail it to you.

	- Dave