Talk:Image Formats - Revision history

Zaimoni at 04:09, 1 September 2010

2010-09-01T04:09:36Z

← Older revision		Revision as of 04:09, 1 September 2010
Line 16:		Line 16:
	This is not right. What if "i" was the last image, TAB[i+1] would point outside the TAB data. The system starts reading PCK data at the offset in the TAB data and stopped when 0xFF was read, that is where the 0xFF byte is for.		This is not right. What if "i" was the last image, TAB[i+1] would point outside the TAB data. The system starts reading PCK data at the offset in the TAB data and stopped when 0xFF was read, that is where the 0xFF byte is for.
	I assume it is ok that I rewrite this a bit.		I assume it is ok that I rewrite this a bit.

			: That is the exception that makes "Typically" right. Clearly if i is the last image then the "next image" doesn't <b>exist</b>, and any reader who was paying attention would know the delta procedure didn't apply.

			: Generally, these articles are written to be read vernacularly, rather than with philosophical or mathematical precision. That said, rewrites that increase clarity are welcome even if they convey the same information as before. -- [[User:Zaimoni\|Zaimoni]], 23:09 Aug 31 2010 CDT

Daiky: /* BDY format algorithm */

2010-08-31T13:25:46Z

BDY format algorithm

← Older revision		Revision as of 13:25, 31 August 2010
Line 10:		Line 10:

	: You're right, a+1 is correct. - [[User:Bomb Bloke\|Bomb Bloke]] 19:54, 19 August 2010 (EDT)		: You're right, a+1 is correct. - [[User:Bomb Bloke\|Bomb Bloke]] 19:54, 19 August 2010 (EDT)

			== PCK ==
			''Typically images are stored sequentially in their archives, so once you know the offset to an image and the image after that you can then read out "x" number of bytes starting at TAB[i] (where "x" is TAB[i+1]-TAB[i] and "i" is the index of the image you wish to view).''

			This is not right. What if "i" was the last image, TAB[i+1] would point outside the TAB data. The system starts reading PCK data at the offset in the TAB data and stopped when 0xFF was read, that is where the 0xFF byte is for.
			I assume it is ok that I rewrite this a bit.

Bomb Bloke at 23:54, 19 August 2010

2010-08-19T23:54:02Z

← Older revision		Revision as of 23:54, 19 August 2010
Line 8:		Line 8:

	~ [[User:Renegrade\|Renegrade]] 10:23, 19 August 2010 (EDT)		~ [[User:Renegrade\|Renegrade]] 10:23, 19 August 2010 (EDT)

			: You're right, a+1 is correct. - [[User:Bomb Bloke\|Bomb Bloke]] 19:54, 19 August 2010 (EDT)

Renegrade: /* BDY format algorithm */

2010-08-19T14:23:57Z

BDY format algorithm

← Older revision		Revision as of 14:23, 19 August 2010
Line 6:		Line 6:

	It appears to be "read a+1 bytes" for BDY files, which makes sense. If this were not the case, the value of '0' would mean "read 0 bytes and draw", which would be wasting a whole code.		It appears to be "read a+1 bytes" for BDY files, which makes sense. If this were not the case, the value of '0' would mean "read 0 bytes and draw", which would be wasting a whole code.

			~ [[User:Renegrade\|Renegrade]] 10:23, 19 August 2010 (EDT)

Renegrade: BDY format algorithm

2010-08-19T14:22:24Z

BDY format algorithm

New page

== BDY format algorithm ==

The following line isn't quite right:

''If "a" is 129 or greater, then draw 257-a pixels of the next byte; otherwise, '''read "a" bytes''' from the file and draw those colors sequentially.''

It appears to be "read a+1 bytes" for BDY files, which makes sense. If this were not the case, the value of '0' would mean "read 0 bytes and draw", which would be wasting a whole code.