Save Image 2.3d

[191Brian]

Hi @SMcNeill

Oh sounds like you have your hands full at the moment with some stressful situations, take care of yourself and I hope your sister gets better. Alzheimers is really tough to deal with.
No rush on save image whenever it  suits your situation.

Right now, I’m stuck down at my mom’s, watching over her.  (She has early onset Alzheimers and has to be monitored 24/7.). Usually my sister takes her about half the time, but the doctors just diagnosed her with breast cancer.  She’s got to go talk to the surgeons on the 30th of this month, so I’ll be stuck here for at least another month.  If things settle down in a few weeks, I’ll try and set aside time to make SaveImage Option _Explicit compatible.

[mohai]

Hello all,

First of all, I wish Steve and all his relatives are well.

The library is great. It is full of interesting and useful features.

I am doing a small project and want to export some pictures to PNG and BMP format.
Your library is great for that but, my program is taking longer and longer to compile now.
I want to make a "light" version so, deleting all the functions I will not use.

I hope you do not mind whether I modify it.

[SMcNeill]

Feel free.  That’s why I shared it, for others to use and enjoy.  ;)

[mohai]

Feel free.  That’s why I shared it, for others to use and enjoy.  ;)

Thanks  lot.
I made a "Save Image Light" from it with the routines to save PNGs and BMPs only.
It works great.
By the way, I did some minors modifications here an there (REM to redundant lines and correct a small bug)

[Richard Frost]

What a super-handy-dandy program!

I've used it to:
1) downsize some of my chess sets so they load faster. MSpaint didn't preserve the alpha
    background.
2) automate the conversion of thousands of picture files for optimal display on my phone
    (320x480), along with maptriangle for rotation.

I'll probably find other uses for it, like taking screenshots.

Thanks, Steve!

[Cobalt]

@SMcNeill  Just FYI the recent adjustment\fix to functions has created an issue with your BM file.
More specifically QB64 has an issue with this line now:

    IF PNGExport <> 0 THEN

within the PNGExport function

[Cobalt]

Also, How much work would it be to allow exported images to be larger than 32767 pixels on an axis?

[SMcNeill]

Also, How much work would it be to allow exported images to be larger than 32767 pixels on an axis?

What type of images?  PNG, BMP, JPG, or GIF?  Each has their own specification, and I don't remember what all the various limits are off the top of my head.

Many of the older image types are stuck with 32-bit specifications.  32,767 x 32,767 pixels x 4 bytes per pixel for 32-bit images gives a 4GB file size -- the absolute most you can push into an UNSIGNED LONG.  Easiest solution here would be to just do a pure memdump of your oversized image yourself, using DEFLATE and INFLATE on it, and save it as a custom data format.  It's the way I'd go with it, if I was writing a program to *ONLY* run in 64-bit OSes.

[Cobalt]

The Tile List I'm working with has 1064 tiles at 32pixels a tile which come to 34048x32.
the current layout is 8 tiles wide by 133 rows.
though that includes Map tiles and Item tiles so I may just split it up into 2 tile sheets.

I like keeping it 1 tile high and just really long to simplify the selection process. Just worrying about the X location of a tile instead of both X and Y.

[SMcNeill]

I don't think it's going to work for you like that, @Cobalt. 

Here's a simple little routine which does a screen dump to a file for us, and then restores that screen back for us...   Take a look at it at work.

Code: QB64: [Select]

1. Screen _NewImage(1024, 720, 32)
2. Dim Shared foo, q$, q2$
3. foo = _NewImage(100000, 32, 32)
4.  
5. _Dest foo
6. For i = o To 100000
7.     Line (i, 0)-Step(0, 31), &HFF000000 + Rnd * &HFFFFFF
8. Next
9. _Dest 0
10.  
11. ImageDump32 foo, "fooImage.dmp"
12. Print "Image created and saved to disk..."
13. Print
14. Print "Now loading..."
15. Print
16.  
17. NewImage = ImageRestore32("fooImage.dmp")
18.  
19.  
20. For i& = 0 To 100000 Step 100
21.     Locate 5, 1: Print i&; "/"; 100000
22.     _PutImage (0, 100)-(1024, 132), NewImage, 0, (i&, 0)-Step(1024, 32)
23.     _Limit 60
24.     _Display
25. Next
26.  
27.  
28. Sub ImageDump32 (image, file$) 'only for 32-bit screens
29.     Dim m As _MEM: m = _MemImage(image)
30.     w&& = _Width(image): h&& = _Height(image)
31.     t$ = Space$(m.SIZE): _MemGet m, m.OFFSET, t$
32.     t2$ = _Deflate$(t$)
33.     f = FreeFile
34.     Open file$ For Output As #f: Close f 'erase any old file with this name
35.     Open file$ For Binary As #f
36.     Put #f, , w&&
37.     Put #f, , h&&
38.     Put #f, , t2$
39.     Close f
40.     _MemFree m
41. End Sub
42.  
43. Function ImageRestore32 (file$) 'only for 32-bit screens
44.     f = FreeFile
45.     Open file$ For Binary As #f
46.     Get #f, , w&&
47.     Get #f, , h&&
48.     t2$ = Space$(LOF(f) - 16)
49.     Get #f, , t2$
50.     Close f
51.     t$ = _Inflate$(t2$)
52.     tempImage = _NewImage(w&&, h&&, 32)
53.     Dim m As _MEM: m = _MemImage(tempImage)
54.     ImageRestore32 = tempImage
55.     _MemPut m, m.OFFSET, t$
56.     _MemFree m
57. End Function
58.  

At first, I was curious if *I* was the one who made a mistake in my code somewhere, but being the flawless and perfect programmer that I am, I quickly ruled that option out.  ;D

Taking all the screen dump and files size/load stuff out, we end up with this really simple little program here:

Code: QB64: [Select]

1. Screen _NewImage(1024, 720, 32)
2. foo = _NewImage(100000, 32, 32)
3.  
4. _Dest foo
5. For i = o To 100000
6.     Line (i, 0)-Step(0, 31), &HFF000000 + Rnd * &HFFFFFF
7. Next
8. _Dest 0
9.  
10.  
11. For i& = 0 To 100000 Step 10
12.     Locate 5, 1: Print i&; "/"; 100000
13.     _PutImage (0, 100)-(1024, 132), foo, 0, (i&, 0)-Step(1024, 32)
14.     _Limit 60
15.     _Display
16. Next

Let it run and watch what happens when it gets up around that 33k pixel mark...  i& keeps incrementing, but the screen stops updating -- it's ran out of image to copy from!

If I had to take a guess, without looking at the source, I'd say that limit is QB64's max image limit just as much as anything else.  Unless somebody finds something wrong with the simple code above, I think what you're looking for is beyond the limits of QB64's images.  You're going to have to go at least 2 layers deep, or else write 2 different image files, to make things work properly, I'd imagine.

[SMcNeill]

Updated to version 2.3d.

Only one little change here -- a fix to the issue which pops up in the latest version of QB64 due to the changes in FUNCTION and recursive calls.  If you're using a version of QB64 before 2.0, then you don't need to worry about this download.  For all users of QB64 v2.0 and up, you'll need this package instead of the old one.  (Note, older users can use SaveImage 2.3d just fine, so there's no reason NOT to download and use this one.  It's just not *required* for you to upgrade above 2.3c, unless you're using QB64v2.0 or newer.)