xv problems please note the newsgroups recent discussion about xv s problems were held in some newsgroup here is some text users of xv might find interesting i have added more to text to this collection article so read on even you so my articles a while ago i hope author of xv corrects those problems as best he can so fine program xv is that it is worth of improving i have also minor ideas for bit xv e mail me for them any misundertanding of mine is understandable juhana kouhia clip deleted note that xv saves only bit rasterized images that means that the saved jpegs are just like jpeg to gif to jpeg quality also there s three kind of bit quantizers your final image quality depends on them too this were the situation when i read jpeg faq a while ago imho it is design error of xv there should not be such confusing errors in programs there s two errors xv allows the saving of bit rasterized image as jpeg even the original is bit saving bit rasterized image instead of original bit should be a special case xv allows saving the bit rasterized image made with any quantizer the main case should be that xv quantizes the image with the best quantizer available before saving the image to a file lousier quantizers should be just for viewing purposes and a special cases in saving the image if at all clip clip deleted it is limit of xv but not limit of design it is error in design it is error that bit quantized rasterized images are stored as jpegs jpeg is not designed to that as matter of fact i m sure when xv were designed bit displays were known it is not bad error to program a program for bit images only at that time but when bit image formats are included to program the whole design should be changed to support bit images that were not done and now we have the program violate jpeg design and any bit image format the program has human interface errors otherway is to drop saving images as jpegs or any bit format without clearly saying that it is special case and not expected in normal use deleted clip some new items follows clip i have seen that xv quantizes the image sometimes poorly with best option than with default option we have the reason surely is the quantizer used as best it is surprise the same than used in ppmquant if you remember i have tested some quantizers in that test i found that rlequant with default is best then comes djpeg fbmquant xv our default in that order in my test ppmquant suggeeded very poorly it actually gave image with bad artifacts i don t know is ppmquant improved any but i expect no so use of xv s best option is not very good idea i suggest that author of xv changes the quantizer to the one used in rlequant i m sure rle people gives permission another could be one used in imagemagick i have not tested it so i can say nothing about it clip clip some minor bugs in human interface are key pressings and cursor clicks goes to a buffer often it happens that i make click errors or press keyboard when cursor is in the wrong place it is very annoying when you have waited image to come about five minutes and then it is gone away immediately the buffer should be cleaned when the image is complete also good idea is to wait few seconds before activating keyboard and mouse for xv after the image is completed often it happens that image pops to the screen quickly just when i m writing something with editor or such those key pressings then go to xv and image has gone or something weird in the color editor when i turn a color meter and release it xv updates the images it is impossible to change all rgb values first and then get the updated image it is annoying wait image to be updated when the setting are not ready yet i suggest of adding an apply button to update the exchanges done clip
