Hi Graham, You can write your own code to make sure that a file doesn't exist already. Before you export a snapshot to it, you can delete the file and check that it has been created again afterwards. You can also check "the result" and "it" for errors at certain points. I wouldn't want RunRev to show some error message by itself. I prefer to have full control over error messages and I don't think that the current ways of (silent) error reporting should be changed.
You can write a script to check that the user selected an area within the target rect. If not, don't apologise for the user's mistakes but just show your custom error message. -- Best regards, Mark Schonewille Economy-x-Talk Consulting and Software Engineering Homepage: http://economy-x-talk.com Twitter: http://twitter.com/xtalkprogrammer KvK: 50277553 New: Download the Installer Maker Plugin 1.6 for LiveCode here http://qery.us/ce On 14 apr 2011, at 10:31, Graham Samuel wrote: > Mark, thanks for the reply, but I'm amazed that you are happy with the idea > of silent failure of **any** operation. > > The thing is, I'm using 'snapshot' to create the output of my app (it's a > portion of a bitmap that's been chosen by my user, to simplify somewhat). If > nothing appears, then I need at least to make my excuses to the user and > asking him/her to try again. As it is, to detect that the operation has > failed means means more code. Maybe I should be using 'crop' followed by some > separate file-exporting operation: then at least I'd know by conventional > means if the file couldn't be written. In general, I don't yet understand how > one detects failures of operations based on URLs. But I'm a newbie in this > respect. > > Graham > _______________________________________________ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
