it's really not a big thing, but as usual when playing with images I had a crash for forgetting the screenres call at image creation.
It beeped at BLOAD function call in my case recently so I've been to the BLOAD doc page. It's very well done with most frequent reasons of run-time failure. Just I found the exposure of the case not well separated enough.
It's like that:
Runtime errors:
BLoad throws one of the following runtime errors:
(1) Illegal function call
dest was not specified or was null (0), and no graphics screen was set.
I don't know if it's better rendered and still true with something like that:
The most current cause of failure is in my mind explained by the first sentence, that's why I'm thinking of it. But I don't know exactly what the second sentence mean. Does this mean that BLOAD won't crash if the dest is NULL and a graphics screen is set?Runtime errors:
BLoad throws one of the following runtime errors:
(1) Illegal function call
no graphics screen was set at image creation time
dest was not specified or was null (0), (and?? no graphics screen was set).
Not a big issue, just clarification of a usual case, thanks.