AntiAliasing/Pallet different on different machines.
-
- Posts: 6
- Joined: Mon Oct 13, 2008 4:50 pm
AntiAliasing/Pallet different on different machines.
Not saying this is a TRichview issue, but hoping you may be able to shed some light regarding what may be going on. We have many test machines on which regression testing is performed. In this case the test is writing some sample text via TRichView and saving the image to a file (the attached pngs). The images are the same except for a slight pallet shift in the anti-aliasing which the human eye would not catch. The text files are of the images' metadata and show basically the same thing except for the values of the pixels making up the histogram. Files generated inside VMs on the same or similar host servers always render the same way, but a different host server may have different histogram values as indicated in the txt files. Any ideas what may cause this.? OS is the same in each case. Not sure if SSE could be a factor or not. Just looking for what may explain the differences and trying to see if we can make the results more consistent.
- Attachments
-
- TestInsertTextBoxes_3.png (3.42 KiB) Viewed 12694 times
-
- Machine2.txt
- (4.06 KiB) Downloaded 1153 times
-
- Machine1.txt
- (4.03 KiB) Downloaded 1175 times
-
- Image001.png (3.41 KiB) Viewed 12694 times
-
- Site Admin
- Posts: 17557
- Joined: Sat Aug 27, 2005 10:28 am
- Contact:
Re: AntiAliasing/Pallet different on different machines.
I am not sure, but probably the results depend on the system ClearType setting.
(in Windows 10, they can be found by typing "ClearType" in the Windows search box)
(in Windows 10, they can be found by typing "ClearType" in the Windows search box)
-
- Posts: 6
- Joined: Mon Oct 13, 2008 4:50 pm
Re: AntiAliasing/Pallet different on different machines.
Thanks for the suggestion. ClearType does effect what is rendered, but I now the rendering differences seem to be the result of several factors which might include the graphics card of host computer. In any case, it is definitely not a TRichView issue.