I have the resolution code essentially complete. Unfortunately, I'm
running into the float vs. double problem I had with the paper
conversion, so verification is taking a bit longer (I'm having to
repeat the baseline with float conversion to be sure that I'm getting
the same results). I need to make sure that there's not some gross
little detail somewhere that I've missed.
Once I've verified this round of results, I will check the code in
(again, there will be some very minor output changes due to the float
vs. double problem, but this should be no more than a difference of 1
on a 0-65535 scale) and then valgrind it. I've already smoke tested
one printer and found nothing; the odds are that the valgrind pass
will check out, but I'll do it post-commit.
This now leaves only the bad one -- the channel definitions. That's
ugly because it's a very deeply nested data structure.
After that, it's going to be a matter of cleanup. One problem is that
the parser's not very robust -- minor differences in the XML files
will probably break it. I'll want to clean all that up before release.
--
Robert Krawitz <
rlk@...>
Tall Clubs International --
http://www.tall.org/ or 1-888-IM-TALL-2
Member of the League for Programming Freedom -- mail
lpf@...
Project lead for Gutenprint --
http://gimp-print.sourceforge.net"Linux doesn't dictate how I work, I dictate how Linux works."
--Eric Crampton
-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php_______________________________________________
Gimp-print-devel mailing list
Gimp-print-devel@...
https://lists.sourceforge.net/lists/listinfo/gimp-print-devel
