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 On Thu, 14 Apr 2011 03:21:36 +0200, Mark Schonewille <m.schonewi...@economy-x-talk.com> wrote: > > Hi Graham, > > I can confirm all, but I have to say that 2 and 3 are logical and expected. I > wouldn't this to be different. I can imagine that 1 is a little annoying and > it would definitely be helpful to be able to import snapshots from closed > stacks. > > I can add a fourth problem: import snapshot doesn't support multiple > monitors, which means you can't create a screenshot of (a part of) your > secondary monitor. > > -- > Best regards, > > Mark Schonewille > _______________________________________________ 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
