Re: the target

2012-09-15 Thread Jacques Hausser
Le 16 sept. 2012 à 02:57, Mark Smith a écrit : > Ok, thanks Mike and Pete. I understand what is going on now. So I guess the > best (and only?) way to keep track of this is: > > on mouseup > stuff the name of the button in a global variable > go stack test > > then in "test" retrieve the bu

Re: the target

2012-09-15 Thread Mark Smith
Ok, thanks Mike and Pete. I understand what is going on now. So I guess the best (and only?) way to keep track of this is: on mouseup stuff the name of the button in a global variable go stack test then in "test" retrieve the button name from the global variable. Doesn't sound too complicat

Re: the target

2012-09-15 Thread Peter Haworth
What Mike said. I found this confusing at first but just think of it being true until another engine message is generated, then that message rests the target. So if the button on your first card had a mouseUp script that called your handler "xyz", then "xyz" would report your button as the target

Re: the target

2012-09-15 Thread Mike Bonner
The target where the MOUSEUP originated is the button. The target that recieved the opencard is the card, so the opencard handler reports that. If you change your source button handler to go stack "test" pass mouseup Then add a mouseup handler to the card script of the mainstack on mouseup put

the target

2012-09-15 Thread Mark Smith
I have a question about "the target" According to the docs "Returns the object which received the message that started execution." And "Use the target function within a message handler to determine which object originally received the message." So why, when I do the following, does it return "c

Re: Scrolling beyond 32k pixel limit?

2012-09-15 Thread ha...@exformedia.se
Maybe you an setup your photos so you don't need to have all in one group. In fact I don't think you need more than three the actual card the card to the left and the on to the right. When you scrolled to the next card you can switch the left, middle and right cards. Just an idea :-Håkan 1

Re: Saving in lageacy format

2012-09-15 Thread Peter Haworth
Yes, that was my thought too. Unfortunately, I can't consistantly reproduce the duplicate stack part of the problem. Pete lcSQL Software On Sat, Sep 15, 2012 at 11:24 AM, J. Landman Gay wrote: > What it sounds like is that LiveCode is opening the new copy as a second > s

Re: Saving in lageacy format

2012-09-15 Thread J. Landman Gay
On 9/15/12 2:20 AM, Richmond wrote: On 09/15/2012 02:43 AM, Peter Haworth wrote: Saving a stack file created with 5.5 as a legacy format 2.7 file seems to be broken. This is because there is a format between versions 5.5 and 2.7, and 5.5 saves a "legacy format" that can be opened by versions

Re: Getting rid of a stack password

2012-09-15 Thread Peter Haworth
Interesting, hadn't noticed that was there. I think though that only applies to stacks saved separate from a standalone executable and I'm not building an standalone. Pete lcSQL Software On Thu, Sep 13, 2012 at 7:40 PM, Kay C Lan wrote: > What happens if you use the Sta

Re: Saving in lageacy format

2012-09-15 Thread Dar Scott
I don't know if this will help, but here is a double-check. A file in the 2.7 format will have these leading characters: REVO2700 (And 2.4 will start out with "#!/bin/sh" "# MetaCard 2.4 stack".) It seems I had some trouble at one time saving in legacy format, but I don't remember what it was.

Re: [OT] Looking For OS X Troubleshooting Suggestions 22

2012-09-15 Thread Jim Hurley
Thanks Kay. The "complete external kit" sounds like a particularly good idea. It allows me to test the next step in the process before proceeding. Jim > > Message: 9 > Date: Fri, 14 Sep 2012 10:28:07 +0800 > From: Kay C Lan > To: How to use LiveCode > Subject: Re: [OT] Looking For OS X Troub

[OT] Spam arrest/flow chart

2012-09-15 Thread Mark Schonewille
Jeff, You tried to contact me about flow charts but you don't get my replies because spam arrest blocks my e-mails and I can't enter the correct captcha. I suggest you turn off spam arrest or send me an e-mail from a different address. -- Kind regards, Mark Schonewille Economy-x-Talk Http://ec

Re: Saving in lageacy format

2012-09-15 Thread Richmond
On 09/15/2012 02:43 AM, Peter Haworth wrote: Saving a stack file created with 5.5 as a legacy format 2.7 file seems to be broken. This is because there is a format between versions 5.5 and 2.7, and 5.5 saves a "legacy format" that can be opened by versions such as 4.0. __