Why don you just save parameter information in the image files like FractInt does?
Well, for one thing, this isn’t FractInt. 🙂 Actually, I thought about it. It would be a great way to combine saving the image information and parameters in one compact unit. Unfortunately, .NET doesn’t have the capability (that I know of) to read and write the extra textual blocks of the GIF98a or PNG specifications which would be needed to store such information. And saving the parameters and the palettes by themselves, without the image, takes up much less space. If you’ve never used FractInt, consider it highly recommended. It has also been ported to several different platforms. Personally, I find MM! a lot easier to use, but FractInt is much more versatile and can handle many more fractals than just the Mandelbrot and Julia sets.
Related Questions
- I have a CIELAB workflow. If I want to print image files in CIELAB colorspace can I use ColorPro to select my output profile and rendering intent then just print the files?
- After processing image files using the "Create Searchable PDF" option, I noticed that my PDF files are now Zero KB. What happened?
- Can TFA-JobTech upload the image files to our server?
