Archive-Date: Thu, 1 Jul 1999 01:36:59 +0200
From: Lucas Hart <hartl@ucs.orst.edu>
Reply-To: VMS-MOSAIC@LEVITTE.ORG
Message-ID: <199906302336.QAA08318@ucs.orst.edu>
Subject: single plane display
To: VMS-MOSAIC@LEVITTE.ORG
Date: Wed, 30 Jun 1999 16:36:53 -0800 (PDT)
CC: hartl@ucs.orst.edu
Content-Type: text


Summary: Version 3.3 will not display on a display server with only a
single plane display; version 2-7 does display on such a display server.
The condition appears to be not considered in COLORS.C get_safe_colors()
(and elsewhere?).

Details:

Version 3.3 (w/ patches thru 26-May) built with "out of the box" with:

  DEC TCP/IP Services for OpenVMS AXP Version V4.0 - ECO Level 1
  on a DEC 3000 Model 300L running OpenVMS V6.2

  DECwindows ident is                     DW V1.2-3960215
  DECwindows server ident is              DW T6.2-950505
  DECwindows transport ident is           DW T6.2-950505
  DECwindows xlib ident is                DW V1.2-3960215

  DEC C V5.3-006

(I was impressed - I've had some experience debugging build procedures 
for much simpler applications and appreciate the effort required.)

Attempting to display it to a monochrome "Xterm" gives the following 
error:

  X Error: BadValue (integer parameter out of range for operation)
    Major Opcode:  91
  Caught X Error -- Press RETURN

after which the process runs down.

Displaying to the local DECWindows monochrome monitor, or to another, 
similarly configured Xterm (but color instead of monochrome), does not 
generate any errors.

Mosaic 2-7_5 displays successfully on all three devices.

According to "The X Window System", 3rd ed., opcode 91 is QueryColors
for which:

  The XQueryColor and XQueryColors functions take pixel values in
  the pixel member of XColor structures and store in the structures
  the RGB values for those pixels from the specified colormap.
  ... If a pixel is not a valid index into the specified colormap,
  a 'BadValue' error results.

A portion of the xdpyinfo output for the errant monochrome display 
server (running on a Sun SPARCstation SLC ) shows:

  version number:    11.0
  vendor string:    MIT X Consortium
  vendor release number:    5000
  number of supported pixmap formats:    1
  supported pixmap formats:
      depth 1, bits_per_pixel 1, scanline_pad 32

while xdpyinfo for two other display servers (the same display server 
on a Sun with a color frame buffer, or the local DECWINDOWS display 
server with a monochrome display) both show:

  number of supported pixmap formats:    2
  supported pixmap formats:
      depth 1, bits_per_pixel 1, scanline_pad 32
      depth 8, bits_per_pixel 8, scanline_pad 32

Some fiddling with the source code shows that, for the single plane
system, 
  XOpenDisplay DisplayPlanes() = 1
and, in COLORS.C, the error appears to be caused by get_safe_colors() 
calling XQueryColors() with col.pixel=2.

What source code changes might be required to support a single plane 
display, as does v2.7?


- Lucas Hart             <hartl@ucs.orst.edu>
================================================================================
Archive-Date: Thu, 1 Jul 1999 07:24:57 +0200
Date: Thu, 01 Jul 1999 01:15:11 -0400 (EDT)
From: George Cook <COOK@wvnvaxa.wvnet.edu>
Reply-To: VMS-MOSAIC@LEVITTE.ORG
Subject: Re: single plane display
In-Reply-To: "Your message dated Wed, 30 Jun 1999 16:36:53 -0800 (PDT)" <199906302336.QAA08318@ucs.orst.edu>
To: Lucas Hart <hartl@ucs.orst.edu>
CC: VMS-MOSAIC@LEVITTE.ORG, COOK@wvnvaxa.wvnet.edu
Message-ID: <01JD1681NDG0Z7CKV6@wvnvms.wvnet.edu>
MIME-Version: 1.0
Content-Type: text/PLAIN; CHARSET=US-ASCII

>Summary: Version 3.3 will not display on a display server with only a
>single plane display; version 2-7 does display on such a display server.
>The condition appears to be not considered in COLORS.C get_safe_colors()
>(and elsewhere?).

>A portion of the xdpyinfo output for the errant monochrome display
>server (running on a Sun SPARCstation SLC ) shows:

>      depth 1, bits_per_pixel 1, scanline_pad 32

This display can only have two pixel values (0 and 1), so col.pixel=2
is invalid.

>What source code changes might be required to support a single plane
>display, as does v2.7?

I put a new COLORS.C in the Mosaic anonymous ftp directory on alpha.wvnet.edu.
It has a quick hack which should correct the problem.  A better solution
will have to wait until I get to the office.


George
================================================================================
Archive-Date: Tue, 27 Jul 1999 02:09:40 +0200
Date: Mon, 26 Jul 1999 19:50:12 -0400 (EDT)
From: George Cook <COOK@wvnvaxa.wvnet.edu>
Reply-To: VMS-MOSAIC@LEVITTE.ORG
Subject: Mosaic V3.4 now available
To: VMS-MOSAIC@LEVITTE.ORG
CC: COOK@wvnvaxa.wvnet.edu
Message-ID: <01JE16SGVNUYZ7DKEG@wvnvms.wvnet.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII

Release 3.4 of VMS Mosaic is now available at

    ftp://alpha.wvnet.edu/mosaic/mosaic3_4.zip

It includes the following changes since release 3.3:
-----------------------------------------------------------------------
 o Added support for non-persistent cookies
 o Added a cookie jar management interface
 o Added support for VALIGN in <TR> and <TD>/<TH> tags
 o Added support for <SPACER> tags
 o Added support for MARGINWIDTH, LEFTMARGIN, RIGHTMARGIN,
   MARGINHEIGHT and TOPMARGIN in <BODY> tags
 o Added support for <BLINK> tags
 o Added background processing of images outside view area
 o Added support for TYPE in <UL> tags
 o Added support for ABSMIDDLE, ABSBOTTOM and TEXTTOP alignment
   in <IMG> tags
 o Added support for COLOR in <BASEFONT> tags
 o Added limited support for HEIGHT in <TABLE> tags
 o Added support for using 'O' for '0' in hex colors
 o Changed default vertical alignment in table cells to MIDDLE
 o Changed Back and Forward to also track horizontal scrollbar
 o Changed hotlist popup menu to use multiple columns as needed 
 o Improved table and border width calculations
 o Improved global history file performance
 o Improved support for floating objects in lists
 o Improved parsing of quoted strings in tags
 o Restored support for single plane (monochrome) displays
 o Eliminated hangs caused by external image viewer aborts
 o Removed obsolete preferences from preference file
 o Removed KCMS code
 o Various bug and memory leak fixes
-----------------------------------------------------------------------

The major change is support for non-persistent (i.e. kept only for
the current session) cookies.  Cookie support is controlled via
the COOKIES and ACCEPT_ALL_COOKIES preferences and the cookie
jar manager (select the cookie jar manager icon on the toolbar).

Support for the BLINK tag is controlled via the BLINKING_TEXT and
BLINK_TIME preferences.


George
================================================================================
Archive-Date: Tue, 27 Jul 1999 14:59:49 +0200
Message-ID: <088a01bed82f$9e014b20$d6001c7e@gr-355538.si.com>
From: "Brian Tillman" <tillman@swdev.si.com>
Reply-To: VMS-MOSAIC@LEVITTE.ORG
To: <VMS-MOSAIC@LEVITTE.ORG>
Subject: Re: Mosaic V3.4 now available
Date: Tue, 27 Jul 1999 08:57:43 -0400
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit

>Release 3.4 of VMS Mosaic is now available

George, you are absolutely fabulous!

 Brian Tillman                   Internet: tillman_brian at si.com
 Smiths Industries, Inc.                   tillman at swdev.si.com
 3290 Patterson Ave. SE, MS      Addresses modified to prevent
 Grand Rapids, MI 49512-1991     SPAM.  Replace "at" with "@"
        This opinion doesn't represent that of my company


================================================================================
Archive-Date: Tue, 27 Jul 1999 20:14:48 +0200
Date: Tue, 27 Jul 1999 14:13:46 -0400
From: John Hasstedt <manager@nuclear.physics.sunysb.edu>
Reply-To: VMS-MOSAIC@LEVITTE.ORG
To: VMS-MOSAIC@LEVITTE.ORG
Message-ID: <990727141346.2d80146f@nuclear.physics.sunysb.edu>
Subject: RE: Mosaic V3.4 now available

Mosaic V3.4 and V3.3 do not accept URLs in the form "file:///file.html";
you have to include localhost: "file://localhost/file.html".  Mosaic V3.2
does work with the file:///file.html form.  V3.4 and V3.3 try anonymous
ftp to the local machine.  Can the old behaviour be restored?

Mosaic also ignores an INPUT field if the TYPE is invalid; most other
browsers treat an invalid TYPE as a "text" field.  For example, the
following code does not let you enter a name with mosaic, but does
let you enter a name with lynx and netscape:

<table>
<tr><td>First Name:</td><td><INPUT TYPE="first" NAME=first SIZE=25></td>
<td>Last Name:</td><td><INPUT TYPE="last" NAME=last SIZE=25></td></tr>
</table> 
 
Below is a patch that changes this behavior:

*** [.libhtmlw]htmlform.c;1
--- [.libhtmlw]htmlform.c
**************
*** 142,149
  				return;
  			}
  		} else {	/* error */
! 			free (tptr);
! 			return;
  		}
  	}
  
--- 142,148 -----
  				return;
  			}
  		} else {	/* error */
! 			input_type = InputTypeText;
  		}
  	}
  
--
John Hasstedt                     Internet: John.Hasstedt@sunysb.edu
Physics & Astronomy Department    Phone: 516-632-8169 or 516-632-8153
State University of New York      FAX: 516-632-8573
Stony Brook, NY  11794-3800  USA
================================================================================
Archive-Date: Tue, 27 Jul 1999 20:59:35 +0200
Date: Tue, 27 Jul 1999 13:59:26 -0500
From: David Potterveld (630-252-6589) <POTTERVELD@ANLMEP.PHY.ANL.GOV>
Reply-To: VMS-MOSAIC@LEVITTE.ORG
To: VMS-MOSAIC@LEVITTE.ORG
CC: POTTERVELD@ANLMEP.PHY.ANL.GOV
Message-ID: <990727135926.2ea007ad@ANLMEP.PHY.ANL.GOV>
Subject: RE: Mosaic V3.4 now available

Hi George,

I tried out Mosaic 3.4, and I found two problems:

(1) Visited anchors no longer change color or show up with dashed underlines.
    This is with both the supplied color app resource file, and no resource
    file (to get compiled-in defaults.) It works fine for me with version 3.3.
    This problem is on both VAX and AXP platforms with VMS 6.1.

(2) The hotlist popup menu still is all in one column, even though it is much
    longer than will fit on my screen. (Supposedly fixed in version 3.4).
    This happens on my AXP machine (DEC C compiler V5.5-002). It works properly
    on my VAX machine (DEC C compiler V5.3-006).

______________________________________________________
David Potterveld                potterveld@anl.gov
______________________________________________________
================================================================================
Archive-Date: Tue, 27 Jul 1999 23:41:37 +0200
Date: Tue, 27 Jul 1999 16:49:09 -0400 (EDT)
From: George Cook <COOK@wvnvaxa.wvnet.edu>
Reply-To: VMS-MOSAIC@LEVITTE.ORG
Subject: RE: Mosaic V3.4 now available
In-Reply-To: "Your message dated Tue, 27 Jul 1999 13:59:26 -0500" <990727135926.2ea007ad@ANLMEP.PHY.ANL.GOV>
To: David Potterveld <POTTERVELD@ANLMEP.PHY.ANL.GOV>
CC: VMS-MOSAIC@LEVITTE.ORG, POTTERVELD@ANLMEP.PHY.ANL.GOV, COOK@wvnvaxa.wvnet.edu
Message-ID: <01JE2FW2PREIZ7DKEG@wvnvms.wvnet.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII

>I tried out Mosaic 3.4, and I found two problems:

>(1) Visited anchors no longer change color or show up with dashed underlines.
>    This is with both the supplied color app resource file, and no resource
>    file (to get compiled-in defaults.) It works fine for me with version 3.3.
>    This problem is on both VAX and AXP platforms with VMS 6.1.

Do you have Preferences enabled?  If so, what is the value of
TRACK_VISITED_ANCHORS in mosaic.preferences.  If not, try enabling
them and save the preference file (see Option and File menus).
When they are enabled, the value of TRACK_VISITED_ANCHORS should
be set to True.  If preferences were already enabled, try saving
them in order to update the preference version number (the version
shouldn't make a difference, but it wouldn't be the first time I've
messed something up when adding new preferences).  Also, try starting
Mosaic with /NOPREFERENCES.

Do these systems have the 6.1 C RTL or have you installed a C RTL
patch kit?

If the preferences are set correctly, try changing the following
line in GUI.C:

  if (!checkv || !href)

to

  if (!href)

Note that unlike previous versions of the preference file, the latest
one cannot be used by earlier versions of Mosaic, however 3.4 should
be able to read all earlier versions of the file.

By design, anchors in the cookie jar never change color.

>(2) The hotlist popup menu still is all in one column, even though it is much
>    longer than will fit on my screen. (Supposedly fixed in version 3.4).
>    This happens on my AXP machine (DEC C compiler V5.5-002). It works properly
>    on my VAX machine (DEC C compiler V5.3-006).

If I understand correctly, it does do multiple columns on the VAX, so my
first guess would be that you have different versions of Motif on these
machines.  Can you send me the output generated by using the /VERSION
qualifier on your Mosaic commands?


George
================================================================================
Archive-Date: Wed, 28 Jul 1999 00:23:55 +0200
Date: Tue, 27 Jul 1999 17:23:40 -0500
From: David Potterveld (630-252-6589) <POTTERVELD@ANLMEP.PHY.ANL.GOV>
Reply-To: VMS-MOSAIC@LEVITTE.ORG
To: VMS-MOSAIC@LEVITTE.ORG
CC: POTTERVELD@ANLMEP.PHY.ANL.GOV
Message-ID: <990727172340.2ea007ad@ANLMEP.PHY.ANL.GOV>
Subject: RE: Mosaic V3.4 now available

George,

>>I tried out Mosaic 3.4, and I found two problems:
>
>>(1) Visited anchors no longer change color or show up with dashed underlines.

This was a problem with preferences, which were enabled. The preferences file
was version 1.8. (Call this the "old" file). I started mosaic 3.4, and
immediately saved the preferences to a new file. (Call this the "converted"
file.) I then renamed the preference files to hide them from mosaic, and
started up version 3.4 again. I enabled preferences, and saved them to a
new file. (Call thie the "default") file.
The value of TRACK_VISITED_ANCHORS was:

True (old file), False (converted file), True (default file)

"Diff"ing the default and converted files showed one other difference:
SPLASHSCREEN was True in the default file, but False in the converted file.
(And also False in the old file.)

>>(2) The hotlist popup menu still is all in one column, even though it is much
>>    longer than will fit on my screen. (Supposedly fixed in version 3.4).
>>    This happens on my AXP machine (DEC C compiler V5.5-002). It works properly
>>    on my VAX machine (DEC C compiler V5.3-006).
>
>If I understand correctly, it does do multiple columns on the VAX, so my
>first guess would be that you have different versions of Motif on these
>machines.  Can you send me the output generated by using the /VERSION
>qualifier on your Mosaic commands?
>

You are correct: single column on AXP, multiple column on VAX. Here are the
outputs of mosaic/version:

AXP> mosaic/version
VMS Mosaic version 3.4
The executable was built with image Ident 3.4
on 27-JUL-1999 09:53:58.68 for use with UCX (or UCX compatible) TCP/IP
and was generated using Motif 1.2 and DEC C.
Support for inline JPEG and PNG images is included.

VAX> mosaic/version
VMS Mosaic version 3.4
The executable was built with image Ident 3.4
on 27-JUL-1999 09:54:32.52 for use with UCX (or UCX compatible) TCP/IP
and was generated using Motif 1.2 and DEC C.
Support for inline JPEG and PNG images is included.

I'm not sure whether a DEC-C RTL patch kit was installed; I'll check.

- DHP                        
================================================================================
Archive-Date: Wed, 28 Jul 1999 01:01:33 +0200
Date: Tue, 27 Jul 1999 18:41:25 -0400 (EDT)
From: George Cook <COOK@wvnvaxa.wvnet.edu>
Reply-To: VMS-MOSAIC@LEVITTE.ORG
Subject: RE: Mosaic V3.4 now available
In-Reply-To: "Your message dated Tue, 27 Jul 1999 17:23:40 -0500" <990727172340.2ea007ad@ANLMEP.PHY.ANL.GOV>
To: David Potterveld <POTTERVELD@ANLMEP.PHY.ANL.GOV>
CC: VMS-MOSAIC@LEVITTE.ORG, POTTERVELD@ANLMEP.PHY.ANL.GOV, COOK@wvnvaxa.wvnet.edu
Message-ID: <01JE2IOPQXSKZ7DB3F@wvnvms.wvnet.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII

>>>(1) Visited anchors no longer change color or show up with dashed underlines.

>This was a problem with preferences, which were enabled. The preferences file
>was version 1.8. (Call this the "old" file). I started mosaic 3.4, and
>immediately saved the preferences to a new file. (Call this the "converted"
>file.) I then renamed the preference files to hide them from mosaic, and
>started up version 3.4 again. I enabled preferences, and saved them to a
>new file. (Call thie the "default") file.
>The value of TRACK_VISITED_ANCHORS was:

>True (old file), False (converted file), True (default file)

>"Diff"ing the default and converted files showed one other difference:
>SPLASHSCREEN was True in the default file, but False in the converted file.
>(And also False in the old file.)

SPLASHSCREEN will get set to False if Mosaic was unable to display the
splash screen when it started and preferences are then saved.  Unfortunately,
Mosaic will do this sort of thing for a number of preferences, however
it is not what happened with TRACK_VISITED_ANCHORS.  I will have to
look into it more.

>>>(2) The hotlist popup menu still is all in one column, even though it is much
>>>    longer than will fit on my screen. (Supposedly fixed in version 3.4).
>>>    This happens on my AXP machine (DEC C compiler V5.5-002). It works properly
>>>    on my VAX machine (DEC C compiler V5.3-006).

I found one possible bug in the code.  Apparently someone tried to save
a couple bytes of memory by making one of the Motif parameters be a
"short int".  I failed to notice it.  Try changing the following line
in gui-popup.c:

      int columns;
to

      short int columns;

Although it worked for me as an "int" on both VAX and AXP, it may fail
on some combinations of Motif, C, VMS, VAX/AXP, etc..


George
================================================================================
Archive-Date: Wed, 28 Jul 1999 02:52:56 +0200
Date: Tue, 27 Jul 1999 20:32:49 -0400 (EDT)
From: George Cook <COOK@wvnvaxa.wvnet.edu>
Reply-To: VMS-MOSAIC@LEVITTE.ORG
Subject: RE: Mosaic V3.4 now available
In-Reply-To: "Your message dated Tue, 27 Jul 1999 14:13:46 -0400" <990727141346.2d80146f@nuclear.physics.sunysb.edu>
To: John Hasstedt <manager@nuclear.physics.sunysb.edu>
CC: VMS-MOSAIC@LEVITTE.ORG, COOK@wvnvaxa.wvnet.edu
Message-ID: <01JE2M85OYRSZ7DKEG@wvnvms.wvnet.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII

>Mosaic V3.4 and V3.3 do not accept URLs in the form "file:///file.html";
>you have to include localhost: "file://localhost/file.html".  Mosaic V3.2
>does work with the file:///file.html form.  V3.4 and V3.3 try anonymous
>ftp to the local machine.  Can the old behaviour be restored?

There is a new HTFILE.C in the anonymous ftp directory on alpha.wvnet.edu
which restores the old behaviour.

>Mosaic also ignores an INPUT field if the TYPE is invalid; most other
>browsers treat an invalid TYPE as a "text" field.  For example, the
>following code does not let you enter a name with mosaic, but does
>let you enter a name with lynx and netscape:

><table>
><tr><td>First Name:</td><td><INPUT TYPE="first" NAME=first SIZE=25></td>
><td>Last Name:</td><td><INPUT TYPE="last" NAME=last SIZE=25></td></tr>
></table>
 
>Below is a patch that changes this behavior:

I have added this for the next release.


George
================================================================================
Archive-Date: Wed, 28 Jul 1999 11:49:09 +0200
Date: Wed, 28 Jul 1999 11:49:24 +0200
From: Alain Chappuis <Alain.Chappuis@medecine.unige.ch>
Reply-To: VMS-MOSAIC@LEVITTE.ORG
Subject: Mosaic 3.4 crash when using Comment Card
Sender: Alain.Chappuis@medecine.unige.ch
To: Mosaic <VMS-MOSAIC@LEVITTE.ORG>
Message-ID: <379EEE43.5BDC82B0@medecine.unige.ch>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Hello,

when I like to use the writing Comment Card, (in Help menu)
Mosaic crash?

Here is the produced file log:
Wed Jul 28 11:43:22 1999 - output from process id 00005626
-> Unable to allocate all browser safe colors
-> Could only get 29 of 216 colors
-> Disabling browser safe color support
->
-> Congratulations, you may have found a bug in (your copy of)
-> VMS Mosaic 3.4 on OpenVMS Alpha.
->
-> Remaining page file quota 186576 (page file quota = 200000)
->
-> If you did not read the README.VMS-3_x file carefully before
installing, it
-> might be a good time to do it now.  If there were any compilation or
linking
-> errors, you should try to find the reason for them and correct them.
-> If this does not help, please take note of what happened in as much
detail
-> as possible and send mail to cook@wvnet.edu.
->
-> Your VMS version appears to be V7.2 running on a AlphaStation
255/300.
-> The TCP/IP software is MultiNet.
-> Your Mosaic executable was generated using Motif 1.2-5
-> and was built on 27-JUL-1999 17:20:39.37 with image Ident 3.4
-> using DEC C.
->
-> The logical SYS$LOGIN points to W3:[CHAPPUIS.DECW]
-> The logical SYS$SCRATCH points to W3:[CHAPPUIS]
-> ...exiting VMS Mosaic now.
->
-> %SYSTEM-F-ABORT, abort

Compilation: with DEC C ver 6.00 and Multinet V4.1 Rev A 
AlphaStation 255/300, OpenVMS AXP V7.2

Alain.
--
+----------------------+-------------------------------------------+
| Alain Chappuis       | Responsable du systeme cmu.unige.ch       |
| Analyste programmeur | Responsable des serveurs WEB medecine, JID|
| Universite de Geneve | E-mail : Alain.Chappuis@medecine.unige.ch |
| Centre Medical Univ. | Phone  : +41 (22) [70]25.073              |
| 1, Rue Michel-Servet | FAX    : +41 (22) 347.33.34               |
| CH-1211 Geneve 4     | WWW    : http://www.medecine.unige.ch/   
|       
+----------------------+-------------------------------------------+
================================================================================
Archive-Date: Wed, 28 Jul 1999 12:15:56 +0200
Date: Wed, 28 Jul 1999 06:15:10 -0500
From: "Edward J. Groth" <groth@PUPGG.PRINCETON.EDU>
Reply-To: VMS-MOSAIC@LEVITTE.ORG
To: VMS-MOSAIC@LEVITTE.ORG
Message-ID: <009DBC49.027C9A93.9@PUPGG.PRINCETON.EDU>
Subject: Out until 4-Aug

I will be out of the office and reading email sporadically, if at
all, until August 4, 1999.

If you have a question about graduate studies, please contact
Laurel Lerner, assistant to the director of graduate studies,
laurel@pupgg.princeton.edu.

For general assistance, contact my secretary, Angela Qualls,
angelaq@princeton.edu.

You should receive only one copy of this message. I apologize if
it hits a mailing list!

					- Ed


--

/----------------------------------------------------------------------\
| Edward J. Groth            | Phone: 609-258-4361   Fax: 609-258-6853 |
| Physics Dept., Jadwin Hall | URL: http://pupgg.princeton.edu/~groth/ |
| Princeton University       | SPAN/HEPNET:  PUPGG::GROTH=44117::GROTH |
| Princeton, NJ 08544        | Internet:     groth@pupgg.princeton.edu |
\----------------------------------------------------------------------/

================================================================================
Archive-Date: Wed, 28 Jul 1999 22:59:28 +0200
Date: Wed, 28 Jul 1999 15:59:12 -0500
From: David Potterveld (630-252-6589) <POTTERVELD@ANLMEP.PHY.ANL.GOV>
Reply-To: VMS-MOSAIC@LEVITTE.ORG
To: VMS-MOSAIC@LEVITTE.ORG
CC: POTTERVELD@ANLMEP.PHY.ANL.GOV
Message-ID: <990728155912.2ea007ad@ANLMEP.PHY.ANL.GOV>
Subject: RE: Mosaic V3.4 now available

George,

>I found one possible bug in the code.  Apparently someone tried to save
>a couple bytes of memory by making one of the Motif parameters be a
>"short int".  I failed to notice it.  Try changing the following line
>in gui-popup.c:
>
>      int columns;
>to
>
>      short int columns;

I tried this. Very amusing result; wish I could show it to you. Top portion
of my hotlist is 15 lines of sublists, followed by many individual items.
The display consisted of a single line of some of the sublists, extending
off the screen to the right, overlayed by a single column of some portion
of the remainder of the hotlist. Popping up the hotlist from different
places on the screen produced different results of this general appearance.

I put in a "printf" statement to look at the value of columns, and then it
displayed normally (with columns = 3). I suspect the problem is a compiler
bug. Anyways, I left an invisible hack of this type in my version here, and
I'm satisfied with the way it works, even if I don't understand what's
wrong with the original version. Here are my mods:

--------------------------------- ORIGINAL ----------------------------------
  /* Make it multiple columns, if needed */
  if ((type == XmMENU_PULLDOWN) && (i > 38)) {
      int columns;

      if (i <= 110) {
          columns = (i / 38) + 1;
      } else {
          columns = (i / 51) + 1;
      }
      XtVaSetValues(menu, XmNpacking, XmPACK_COLUMN, XmNnumColumns, columns);
------------------------------------ NEW ------------------------------------
  /* Make it multiple columns, if needed */
  if ((type == XmMENU_PULLDOWN) && (i > 38)) {
      short int columns;
      static char junk[32];
      if (i <= 110) {
          columns = (i / 38) + 1;
      } else {
          columns = (i / 51) + 1;
      }
      sprintf(junk,"%d",columns); /* This fixes wierd AXP error (DHP)*/
      XtVaSetValues(menu, XmNpacking, XmPACK_COLUMN, XmNnumColumns, columns);
-----------------------------------------------------------------------------

- DHP
================================================================================
Archive-Date: Wed, 28 Jul 1999 23:04:54 +0200
Date: Wed, 28 Jul 1999 16:53:06 -0400 (EDT)
From: George Cook <COOK@wvnvaxa.wvnet.edu>
Reply-To: VMS-MOSAIC@LEVITTE.ORG
Subject: Re: Mosaic 3.4 crash when using Comment Card
In-Reply-To: "Your message dated Wed, 28 Jul 1999 11:49:24 +0200" <379EEE43.5BDC82B0@medecine.unige.ch>
To: Alain Chappuis <Alain.Chappuis@medecine.unige.ch>
CC: Mosaic <VMS-MOSAIC@LEVITTE.ORG>, COOK@wvnvaxa.wvnet.edu
Message-ID: <01JE3SQBU9WQZ7DKEG@wvnvms.wvnet.edu>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii

>when I like to use the writing Comment Card, (in Help menu)
>Mosaic crash?

At what point does it crash?  Between when you select Comment
Card and opening the new window?  Or after it opens the window,
but before it displays the card?  Or when you try to submit the
card?

Build Mosaic with the command

@MAKE_MOSAIC TRACE

and send me the output generated when it crashes.


George
================================================================================
Archive-Date: Thu, 29 Jul 1999 00:19:19 +0200
Date: Wed, 28 Jul 1999 18:10:47 -0400 (EDT)
From: George Cook <COOK@wvnvaxa.wvnet.edu>
Reply-To: VMS-MOSAIC@LEVITTE.ORG
Subject: RE: Mosaic V3.4 now available
In-Reply-To: "Your message dated Wed, 28 Jul 1999 15:59:12 -0500" <990728155912.2ea007ad@ANLMEP.PHY.ANL.GOV>
To: VMS-MOSAIC@LEVITTE.ORG
CC: POTTERVELD@ANLMEP.PHY.ANL.GOV, COOK@wvnvaxa.wvnet.edu
Message-ID: <01JE3VIHVZTWZ7DKEG@wvnvms.wvnet.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII

>>I found one possible bug in the code.  Apparently someone tried to save
>>a couple bytes of memory by making one of the Motif parameters be a
>>"short int".  I failed to notice it.  Try changing the following line
>>in gui-popup.c:
>>
>>      int columns;
>>to
>>
>>      short int columns;

>I tried this. Very amusing result; wish I could show it to you. Top portion
>of my hotlist is 15 lines of sublists, followed by many individual items.
>The display consisted of a single line of some of the sublists, extending
>off the screen to the right, overlayed by a single column of some portion
>of the remainder of the hotlist. Popping up the hotlist from different
>places on the screen produced different results of this general appearance.

Yes, it only made matters worse.  I discovered later that it caused
VAX C builds to crash.  I believe I now understand the problem.  I
didn't realize XtVaSetValues does not do argument conversion unlike
the combination of XtSetArg/XtSetValues.  Normally this wouldn't
cause a problem except in the case of odd stuff like "short int".

I put a new GUI-POPUP.C in the anonymous ftp area on alpha.wvnet.edu
which uses XtSetArg and XtSetValues instead of XtVaSetValues.  I
believe it should work in all cases.


George