Here's a sample of what it does:
the first pic is 1x sastraxismooth (4x res - 32x32 to 64x64)
the second is 2x sastraxismooth (16x res - 32x32 to 128x128)
the third is 3x sastraxismooth - makes everything look like a circle, bad, I think (64x res - 32x32 to 256x256)
Here's the attachment:
All contents of the above post that aren't somebody elses are mine, not the property of some media corporation.
(Just a heads-up)
This looks better than your earlier version, still there seems to be work to be done, some corners are sharp yet, the inner corners.
Use
writing software in C++ is like driving rivets into steel beam with a toothpick.
writing haskell makes your life easier:
reverse (p (6*9)) where p x|x==0=""|True=chr (48+z): p y where (y,z)=divMod x 13
To throw away OOP for low level languages is myopia, to keep OOP is hyperopia. To throw away OOP for a high level language is insight.
Hey, all! I just thought of a way to improve the program, which will allow for 1 pixel wide things to still look half decent. I will post the updated prog. soon.
All contents of the above post that aren't somebody elses are mine, not the property of some media corporation.
(Just a heads-up)
btw, i made my own image resizing algoritm, here's samples of two modes:
the topmost was made by psp7 image resizer, the bottom right one is the original
Use
writing software in C++ is like driving rivets into steel beam with a toothpick.
writing haskell makes your life easier:
reverse (p (6*9)) where p x|x==0=""|True=chr (48+z): p y where (y,z)=divMod x 13
To throw away OOP for low level languages is myopia, to keep OOP is hyperopia. To throw away OOP for a high level language is insight.
Reply With Quote
