UnscramblePic.bas - Rotate picture pieces puzzle

[Steffan-68]

Thanks, GareBare!

I have edited all my programs found here on the forum to fix the _INFLATE error in the BASIMAGE created Subs.  

Also -- I've been trying to narrow down in my code exactly what is causes the _INFLATE error.  _INFLATE works on most of my programs without needing the 2nd parameter given.  It seems _INFLATE only needs it (m.SIZE) only in my BASIMAGE SUBs.  Other routines I use _INFLATE don't given the error (like SUBS made with the BASFILE creator).  I thought perhaps the error may happen only when using _MEM stuff (like BASIMAGE uses), but that doesn't look like it  - - the example below does what a BASIMAGE SUB does, but  m.SIZE is not required for _INFLATE to work here. Wonder why _INFLATE fails in in the BASIMAGE created Subs?

_INFLATE works correct here.  m.SIZE not needed.

- Dav

Here's the answer I got back then.


[quote pid="15751" dateline="1683562805"]

[quote pid="15721" dateline="1683475272"]
Has something changed in the '_MEMPUT' command?
The IDE does not report an error, but the error 'Critical Error #300 Line:833 Memory region out of range' is output in the finished compiled program.
With QB64pe V 3.6 the program runs normally, now in V 3.7 this error occurs.

We're investigating It seems like an issue with the change from `zlib` to `miniz`. Your data doesn't successfully decompress with either library, but `zlib` would give you back the partially decompressed data and the correct length of it, where-as `miniz` doesn't give the length of the partially-decompressed data so `btemp$` has the wrong length.
Unfortunately `_Inflate$()` doesn't give an error if the decompression fails so you had no way to know. It really should error, but we probably can't make that change now so we're looking at a fix for `miniz` to give you the correct size. As an alternative to waiting, you code will work in v3.7.0 if you give `_Inflate$()` the size parameter, so `btemp$ = _Inflate$(btemp$, m.SIZE)`.
[/quote]
[/quote]