What happens to LC after rendered Standalone?

Got a LiveCode personal license? Are you a beginner, hobbyist or educator that's new to LiveCode? This forum is the place to go for help getting started. Welcome!

Moderators: FourthWorld, heatherlaine, Klaus, kevinmiller

Post Reply
nbard
Posts: 4
Joined: Sun Nov 01, 2009 11:18 pm

What happens to LC after rendered Standalone?

Post by nbard » Sat Jun 15, 2013 8:05 pm

Hi,
I encountered a surprise this week when working with LC (LC 5.5.4; Win7). I was copying information from one stack to another on a local network. This worked great as long as I stayed within the IDE framework for both stacks, but if saved the sending stack as a standalone, it failed to transfer the information. Once converted to an "*exe", does the card/stack framework on the target end of things no longer make sense? What would be the scripting to get the info to the correct card/field? I have the correct filepath for the directories (since it works via the IDE).

This could be part of the problem: I"m trying to send the info to a substack. I'm working with a script that identifies the target fld this way, allowing for the bogus container names:
on SendInfo
put fld 'A' of cd "B" of stack "C" into fld "D" of cd "E" of stack "F" of URL Blah:/blah/blah/...[name of mainstack].livecode"
end SendInfo

Thanks,
Norval

shaosean
Posts: 906
Joined: Thu Nov 04, 2010 7:53 am

Re: What happens to LC after rendered Standalone?

Post by shaosean » Sun Jun 16, 2013 5:12 am

Once you compile, your stacks are part of the standalone and no longer individual files on the drive so you can't access them via a path..

Post Reply