From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from ejk.cso.uiuc.edu ([130.126.112.162]) by hawkwind.utcs.toronto.edu with SMTP id <25878>; Tue, 9 May 2000 18:51:58 -0400 Received: (qmail 15990 invoked from network); 8 May 2000 23:18:41 -0000 Received: from castle-89.slip.uiuc.edu (HELO uiuc.edu) (ejk@130.126.28.89) by ejk.cso.uiuc.edu with SMTP; 8 May 2000 23:18:41 -0000 Sender: ejk Message-ID: <39174AE2.CEC76A4@uiuc.edu> Date: Mon, 8 May 2000 19:16:50 -0400 From: Ed Kubaitis Organization: CCSO - University of Illinois at Urbana-Champaign X-Mailer: Mozilla 4.72 [en] (X11; U; Linux 2.2.14-5.0 i686) X-Accept-Language: en MIME-Version: 1.0 To: Sam Fans CC: Wily Fans Subject: Re: wily-9libs and sam-9libs on 24-bit Linux display References: <20000417145820.14626.qmail@web3205.mail.yahoo.com> <39173E20.77F0D49@kremvax.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit "Mark H. Wilkinson" wrote: > > Jim Crigler wrote: > > > Before I delve into the particulars, is does anyone know in advance why > > wily-9libson a 24-bit Linux display works fine (modulo I can't use the capslock > > key), while sam-9libs (samterm, actually) balks? They were built in the same > > 9libs hierarchy at the same time. > > Probably because sam allocates new bitmaps for things like pop-up menus while wily > doesn't (not having menus) - if you run the libXg test program does it crash when > it gets to the menu test on the same display? > > libXg just doesn't work with some bitmap depths, notably 15bpp. However, I thought > it worked Ok on 24bpp displays so I'd like to dig a bit more to find out what's > going on. > > -Mark. FWIW, on RH Linux 6.2 recently, I had to backoff 24bpp to 16 to make an ancient (circa 1993-4) version of libXg/samterm functional. -------------------------- Ed Kubaitis (ejk@uiuc.edu) CCSO - University of Illinois at Urbana-Champaign