Thanks Dan,
I've opened bug #79246 for the LockBits issues which, from the unit
tests I added this morning, appears to affect every type of bitmaps.
FYI the problem that affected the (first two lines of) JPEG bitmaps
doesn't happen on any other type of pictures.
On Thu, 2006-08-31 at 09:02
Hello Dan,
It may be unrelated to endian issues (but I still like your answers,
multiple problems are common ;-) as I also found out differences between
Mono on Linux i386 and Windows.
It seems, in my test case, that the first two lines of the decoded jpeg
aren't correct. In the first line all
Hello Dan,
[please c.c. the mailing-list in your answers]
I found a problem with (most) JPEG files where the first two lines had
some bad values. This is fixed in SVN :-)
However my (new) unit tests using LockBits are all failing - even for
bitmaps. Something else is wrong there :-(
Note that
Sebastien,
I just ran the code for reading jpegs on the 1.1.14 build on osx and
it had different results that those that I am currently getting, but
they were still not correct. Hope this helps.
Dan
On 1.1.14 it came out as:
255
255
255
255
77
255
255
75
144
255
75
143
255
73
144
255
74
145
When attempting to read the pixel bytes of a jpg on osx (using the
1.1.17 build just released) I am getting different results on windows
versus osx. Does anybody have any ideas why I am getting these
different results? Any information is very appreciated.
Dan
The code being used is as
Hello Dan,
Did the same code worked on a previous version of Mono ? (if so which
version ?) or are you testing this for the first time ?
Because I recently fixed many endian issues affecting Mac OS X (and
other architectures). It is possible that one of them has broken
something else :-(
I'll
