bob@OHIO-STATE.ARPA (Bob Sutterfield) (06/16/87)
Regarding Xv10r4 under SunOS 3.2 - I'm not sure whether this is a bug
report with a fix, or a request for clarification and enlightenment.
Since I didn't see an answer to the similar question posed by Dave
Curry (davy@pur-ee.uucp), I figure I'll ask again.
I wondered why xsetroot wouldn't do larger bitmaps, even with the
changes from dcmartin@postgres.mit.edu (David C. Martin) to go beyond
the 16x16 limitation. Then in Xlib/XReadBitmapF.c, when looping for
the width, height, x_hot, and y_hot lines in the bitmap, we see:
while ((status = fscanf (file, "#define %80s %2d\n", variable, &value))==2)
{...
The `%2d' specification limits us to 99x99 bitmaps. When the `%2d' is
changed to `%d' the XReadBitmapFile() function seems to successfully
handle arbitrarily-large bitmaps, which is what I needed to put up
fullmoon.bitmap (1152x900) as my background pattern.
Is this an oversight, or an architectural feature, or a performance
sensitive limitation of this implementation, to guard against shipping
huge bitmaps to and fro? What will break if I change the copy of
XReadBitmapFile() in our generally-accessible libX.a?
Thanks for any light you can shed.
------
Bob Sutterfield, Department of Computer and Information Science
The Ohio State University; 2036 Neil Ave. Columbus OH USA 43210-1277
bob@ohio-state.{arpa,csnet} or ...!cbosgd!osu-eddie!bob
soon: bob@aargh.cis.ohio-state.edu