Path: news.nzbot.com!not-for-mail
From: "ericmatteson2003november@hotmail.com" <ericmatteson2003november@hotmail.com>
Newsgroups: alt.tv
Subject: Re: bug report on xwview14.c
Date: Wed, 14 Sep 2011 23:20:59 -0700 (PDT)
Organization: http://groups.google.com
Lines: 59
Message-ID: <c2186037-c608-4607-ae9b-ff6498891aad@v8g2000yqa.googlegroups.com>
References: <d1841ca7-b27c-4721-b8ee-3c5105961f4c@14g2000prv.googlegroups.com>
NNTP-Posting-Host: 66.81.159.47
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
X-Trace: posting.google.com 1316067739 9300 127.0.0.1 (15 Sep 2011 06:22:19 GMT)
X-Complaints-To: groups-abuse@google.com
NNTP-Posting-Date: Thu, 15 Sep 2011 06:22:19 +0000 (UTC)
Complaints-To: groups-abuse@google.com
Injection-Info: v8g2000yqa.googlegroups.com; posting-host=66.81.159.47; posting-account=Tr_DEAoAAACyONYGV3r9H22V5NQYTBXQ
User-Agent: G2/1.0
X-Google-Web-Client: true
X-Google-Header-Order: HUALESNKRC
X-HTTP-UserAgent: Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.8.1.11)
Gecko/20071127 Firefox/2.0.0.11,gzip(gfe)
Xref: news.nzbot.com alt.tv:1089
On Sep 10, 1:30 pm, "ericmatteson2003novem...@hotmail.com"
<ericmatteson2003novem...@hotmail.com> wrote:
> Bugzillia bug report on xwview14.c *.bmp picture viewer program in c
> for
> Linux XWindows.
> ..
> xwview14.c was designed back when monitors were limited to
> 800*600 so its hidden flaw of crashing when enlarging the screen
> was not discovered until a long time later.
> [link to xwview14.c]http://groups.google.com/group/alt.tv/msg/45063d8f167cbf16?dmode=source
> A hidden mistake was discovered in xwview14.c in which more bytes
> were
> initialized than the arrays sizes whenever the window was enlarged
> bigger than 800*600 so xwview14.c CRASHES whenever the window is
> enlarged
> greater then 800*600
> ------------------------------------------------
> xwview15.c adds an if statement to limit initialization of the
> colored
> arrays to their array size so xwview15.c should display large pictures
> in monochrome 1 bit per pixel instead of crashing if their are no
> other
> mistakes.
> [link to xwview15.c]http://groups.google.com/group/alt.tv/msg/60934b3d2ed5536c?dmode=source
> xwview15.c displays 24-bit color up to almost 800*600
> and at 800*600 it barely changes to monochome 1-bit per pixel.
> If your monitor is limited to 800*600 xwview15.c is the best choice.
> ---------------------------------------------------------------------
> xwview16.c still can display up to 24-bit color at exactly 800*600
> pixels
> and switches to monochrome 1-bit per pixel slightly smaller than
> 1024*768
> but requires more RAM than xwview15.c becuse of larger array sizes
> so only use it with a newer monitor of at least 1024*768
> [link to xwview16.c *.bmp viewer program for newer monitors]http://groups.google.com/group/alt.tv/msg/39e8d20c7d79a1ab?dmode=source
> ..
> .
> [link to previous episode of Everybody hates Chris]http://groups.google.com/group/alt.tv/msg/7c5f69aa4ef06c5a
addition to bugzillia bug report.....
The new gimp 2.6 for Linux Gnome XWindows saves its
simple uncompressed bitmaps into a new format. The
value of 32 for bibitcount is unexpected and xwview16.c
gets stuck and its host terminal also freezes and has to be
closed. xwview16 and earlier puts a lot of trust in *.bmp
headers and expects things to ALWAYS be normal under older
traditional rules.
The new xwview17.c does additional error checking on the
.bmp header hoping to prevent crashes to a greater extent.
The new Gimp 2.6 bibitcount of 32 instead of normal 24
uses groups of four bytes instead of three. It looks like the
first three bytes are the actual color bytes so read 3 bytes
then skip one byte for each 32 bit strange GIMP pixel.
xwview had to be upgraded because GIMP has changed the
specification for the best simple *.bmp
[link to xwview17.c *.bmp picture viewer program]
http://groups.google.com/group/alt.tv/msg/0a09a9ffb9648cd9?dmode=source
|
|