Re: how to copy a card?

Thanks, Jacque. Also figured out it can be done with the Project Browser. -- Nicolas Cueto On 8 March 2018 at 15:38, J. Landman Gay via use-livecode < use-livecode@lists.runrev.com> wrote: > Use: > > clone this card > set the name of it to "" > > -- > Jacqueline Landman Gay |

Re: how to copy a card?

Note that one can also copy a card, navigate to another spot in the same or another stack, and paste. The advantage is that the copy can be inserted anywhere in the card suite. This can all be done under script control. Craig -- Sent from:

Re: how to copy a card?

Wouldn't it be great to clone TO a reference? Say, clone this card as "NewCard" to stack "MyStack2"? Bob S > On Mar 7, 2018, at 22:38 , J. Landman Gay via use-livecode > wrote: > > [This message was identified as a phishing scam. Learn about phishing at >

Re: how to copy a card?

Use: clone this card set the name of it to "" -- Jacqueline Landman Gay | jac...@hyperactivesw.com HyperActive Software | http://www.hyperactivesw.com On March 8, 2018 12:24:58 AM Nicolas Cueto via use-livecode wrote: ?Need a new

how to copy a card?

​Need a new card, and want it to be an exact copy (other than the card title) of an existing card. How yo do this in LC? Thank you. -- Nicolas Cueto ​ ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe,

Re: How to copy a card you can't open - corrupted fonts

-revolution.278305.n4.nabble.com/Re-How-to-copy-a-card-you-can-t-open-corrupted-fonts-tp3469978p3471018.html Sent from the Revolution - User mailing list archive at Nabble.com. ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url

Re: How to copy a card you can't open - corrupted fonts

I just found out why LiveCode would crash whenever I tried to open one of the cards in the stack. It turns out there was a corrupted font being used in the suspect card. Solution (Mac OS): 1. Open Font Suitcase in your app folder. 2. Select all fonts 3. Run the validate fonts command 4. Check

Re: How to copy a card you can't open - corrupted fonts

fonts? Have a nice weekend! Al -- View this message in context: http://runtime-revolution.278305.n4.nabble.com/Re-How-to-copy-a-card-you-can-t-open-corrupted-fonts-tp3469978p3471013.html Sent from the Revolution - User mailing list archive at Nabble.com

Re: How to copy a card you can't open - corrupted fonts

fonts? Have a nice weekend! Al -- View this message in context: http://runtime-revolution.278305.n4.nabble.com/Re-How-to-copy-a-card-you-can-t-open-corrupted-fonts-tp3469978p3471018.html Sent from the Revolution - User mailing list archive at Nabble.com

How to copy a card you can't open

I have a stack with three cards. I pulled this stack out of many that was in my application. If I go to the last card in this stack LiveCode crashes every time. How can I figure out what is in this card which is causing LiveCode to crash and delete whatever it is?

Re: How to copy a card you can't open

william humphrey wrote: I have a stack with three cards. I pulled this stack out of many that was in my application. If I go to the last card in this stack LiveCode crashes every time. How can I figure out what is in this card which is causing LiveCode to crash and delete whatever it is? Are

Re: How to copy a card you can't open

Thanks. In the application browser I made everything on that card invisible and it still couldn't be opened without crashing. On Mon, Apr 18, 2011 at 3:59 PM, Richard Gaskin ambassa...@fourthworld.comwrote: william humphrey wrote: I have a stack with three cards. I pulled this stack out of

Re: How to copy a card you can't open

But I found out that deleted the main fld which contained, I thought, only text has made it possible to open the card. So this means that there was text in that field which LiveCode couldn't deal with. ___ use-livecode mailing list

Re: How to copy a card you can't open

Thanks for your help. It wasn't the text in the field. It was the field itself. A basic table field with some tab stops set. Interesting flaw in LiveCode. If I knew where to send the stack to for a bug report I would. On Mon, Apr 18, 2011 at 3:59 PM, Richard Gaskin

Re: How to copy a card you can't open

william humphrey wrote: Thanks for your help. It wasn't the text in the field. It was the field itself. A basic table field with some tab stops set. Interesting flaw in LiveCode. If I knew where to send the stack to for a bug report I would. Glad you got that sorted out. Interesting problem,

Re: How to copy a card you can't open

No. The table field had nine stops. Set like 45,150,300,345,390,595,646,705 and text Helvetica 9 point. I just re-built it. On Mon, Apr 18, 2011 at 4:32 PM, Richard Gaskin ambassa...@fourthworld.comwrote: william humphrey wrote: Thanks for your help. It wasn't the text in the field. It was

Re: How to copy a card you can't open

I was going to say, Suppress Messages and Suppress Errors before opening the stack/card, but it looks like you have things figured out. Jacque has said in the past that a corrupted stack is virtually unheard of in Livecode, so if you have a copy of the old one that was crashing, I would sure

Re: How to copy a card you can't open

On 4/18/11 4:48 PM, Bob Sneidar wrote: I was going to say, Suppress Messages and Suppress Errors before opening the stack/card, but it looks like you have things figured out. Jacque has said in the past that a corrupted stack is virtually unheard of in Livecode, so if you have a copy of the old

Re: How to copy a card you can't open

I tried deleting the text in the field and that didn't stop the crashes. I had to delete the whole field. Even weirder, I went to a back-up that was nearly a year old and found the same problem. Deleting the field and then re-creating it fixed the error I have no back-up to look at to check but I

Re: How to copy a card you can't open

we'd all like to know how you did it. The engine can't do that yet. On 18 April 2011 18:25, william humphrey b...@bluewatermaritime.com wrote: I tried deleting the text in the field and that didn't stop the crashes. I had to delete the whole field. Even weirder, I went to a back-up that was