Page 3 of 3
Re: A bug in the export snapshot command
Posted: Tue Sep 28, 2021 7:13 pm
by RCozens
SparkOut wrote: Tue Sep 28, 2021 7:09 pm
On Windows 9.6.5_64 bit version, I get the same broken gif snapshotted, whether output to file or to a newly created image.
Ah, bless you SparkOut! I am not alone.
Thanks for checking.
Re: A bug in the export snapshot command
Posted: Tue Sep 28, 2021 7:33 pm
by richmond62
Obviously a Windows problem.
Re: A bug in the export snapshot command
Posted: Tue Sep 28, 2021 7:42 pm
by Klaus
RCozens wrote: Tue Sep 28, 2021 7:11 pmThat is the essence of my question Klaus: Why can't LiveCode resolve the "as type" argument at runtime? I have the workaround in the form of a switch, but wonder if there is a specific reason why "as type" can't be resolved at runtime when so many other command arguments can be.
Not a big issue; just an idle wondering.
OK, maybe a good reason to file an "enhancement request" for this.
Re: A bug in the export snapshot command
Posted: Wed Sep 29, 2021 2:19 am
by RCozens
richmond62 wrote: Tue Sep 28, 2021 7:33 pm
Obviously a Windows problem.
I was going to ask what platform you are running.
Would you be willing to try running the logic from my stack (364KB)?
If so, send me an eAddress privately and I will send you a copy.
Re: A bug in the export snapshot command
Posted: Sat Oct 02, 2021 6:21 pm
by RCozens
richmond62 wrote: Tue Sep 28, 2021 7:33 pm
Obviously a Windows problem.
Richmond has run Serendipity Editors on MacOS, and can create GIF files from screen rectangle snapshots.
I have modified the script so that screen snapshots can only be exported on MacOS.
If anyone would like to test this on Linux, eMail me privately with an eAddress and I will send you a copy that allows screen snapshots to be exported to GIF files on that platform.
Cheers!
Re: A bug in the export snapshot command
Posted: Sat Oct 09, 2021 9:10 pm
by RCozens
I tried to report this as a bug today, and I seem to have encountered a bug in the bug reporting system.
I created a simple example stack and listed 10 steps for testing it (the later now comments in the stack script). I've attached the stack if anyone wants to check it out.
Anyway, the bug entry screen lists sections 1 - 7. I completed sections 1 - 6, and then selected the submit bug report button, which is located directly under the "7". I got an error saying I needed to go back and enter a Windows version #. I go back to the screen, and once again I see no place to enter the Windows version. I tried this three times. Am I missing something?
Re: A bug in the export snapshot command
Posted: Sat Oct 09, 2021 11:49 pm
by mwieder
Rob-
It's question/section #4.
Re: A bug in the export snapshot command
Posted: Sun Oct 10, 2021 6:24 pm
by RCozens
mwieder wrote: Sat Oct 09, 2021 11:49 pm
It's question/section #4.
Thank you kindly. It's filed as Bug 23370
Cheers!
Re: A bug in the export snapshot command
Posted: Sun Oct 10, 2021 7:58 pm
by RCozens
Klaus wrote: Tue Sep 28, 2021 7:42 pm
OK, maybe a good reason to file an "enhancement request" for this.
Enhancement request #23371 has been filed.
Re: A bug in the export snapshot command
Posted: Thu Oct 21, 2021 7:05 pm
by RCozens
RCozens wrote: Tue Sep 28, 2021 7:11 pm
Why can't LiveCode resolve the "as type" argument at runtime? I have the workaround in the form of a switch, but wonder if there is a specific reason why "as type" can't be resolved at runtime when so many other command arguments can be.
Here's the answer: There is another syntax for the export command
In this command the previously-selected image is exported in GIF format (or PNG or JPEG or paint, depending on word two of the command). Methinks "export imageType to file fileName" would be more complicated for LiveCode to resolve at runtime than "export image imageName to file fileName as imageType".