Updated. Fixed bugs in functions for working with images.

Ok, I'll try to fix the functions and add a description (you can find it in the Mathcad Help).

Uni, thanks again for the fast debugging response.

However, here are some issues.
- READBIN: in some situations, changes in the sheet trigger the results to become wrong. Manual re-calculation via toolbar button sets the results back to correct values, but otherwise they persist on the sheet. I attach two screenshots, the upper before re-calculation and the lower after. No other difference between these pictures, just pressed the update button. The sm-sheet is included in the zip. The problem is completely reproducible with the given example.

- READBIN: The docs refer to default values for endian, rows, skip and rows. How is the user expected to adress these defaults? Do you plan to provide READBIN(1) as in Mathcad? What would then be the default type?

- READ_xxx: These functions seem to insist on 32bpp images, at least, the one in the attached zip fails to be read in. It is a screenshot, which I intended to use instead of the not so colorful school logo.
The image region is not so picky about that, the image can be displayed without problems. However, if a read statement fails and then the result of that failed op is fed to the image, SMath crashes.

Edited by user 05 May 2013 00:41:56(UTC)  | Reason: Not specified

That I don't understand. It seems that reading is the same file, but with a different content. Below is running another writing function and it can change the data. Try to disable or enable the calculation for one of them (WRITEBIN). It is better to use a different file for testing in one sheet.


I forgot to remove it when copying, but it is possible to have a simplified version of the function.

The update resolved the crash issue. I was irritated by the fact that the read operation did not complain at all, but subsequent ops like asking for the number of rows gave the image format error message. That was due to the default setting of symbolic optimization, i.e. delayed execution of the read op. Obviously, just assigning the result of a read operation to some variable is no read test at all if in symbolic mode.

I am tired of repeating the issue of visually different operators for sym/num assignment and evaluation. Andrey seems to have good reasons for refusing even to give us back the arrow for symbolic evaluation. Is that protected by Mathcad patents?

Updated. wfile(3) and rfile(2) added.

Edited by user 06 May 2013 20:10:34(UTC)  | Reason: Not specified

Updated. DocumentDirectory() added. Try now.

Updated. Play() function added (for wav files).

Edited by user 14 October 2013 23:54:24(UTC)  | Reason: Not specified

I don't understand the problem and do not recommend to use the CurrentDirectory() function for this purpose. If the operating system denies write access, then I can't workaround this. I'm not sure that administrative privileges confirmation during execution is a good idea.

Edited by user 27 March 2014 12:25:00(UTC)  | Reason: Not specified

Supposedly fixing this specific (mis)behaviour by simply returning error with clear message would be enough, no need to emit some unexpected dialogs? Suppose the scenario when a sheet has quite a some different IO operations to a number of locations; and this has a potential of emitting endless series of such dialogs. Also, aquiring priveleges may end up in yet another software capable of hosting viruses...