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 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 01:10, Graham Samuel wrote: > I'm using 'export snapshot' and finding stuff that doesn't seem to be in the > docs, nor did an archive search turn up anything. However I can never rule > out finger trouble on my part. > > Can anyone confirm the following: > > 1. You can't export a snapshot from a card in a substack which isn't open - > you have to 'go to' the stack first to activate it. The thing you're > snapshotting can be off the screen, though (with a loc like 10000,10000). > > 2. If the rect you specify for the snapshot is not actually within the image > you're snapshotting, the export fails silently. Neither 'the result' nor 'it' > seem to report any problems, but the file is not created. > > 3. There is no report if a file is overwritten by an export snapshot - > instead you have to check that the file path is unique by using 'exists' > separately. Or maybe this is a consequence of using URL "binfile:... > > As usual, grateful thanks for any light shed or assumptions corrected > > Graham _______________________________________________ use-livecode mailing list [email protected] Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
