Multiple revCursors substacks added to standalone

For a while now (LC 9.x) I have been finding that making a standalone sometimes adds multiple copies of revCursors to the standalone. One copy as a substack of the mainstack is expected, but under some unknown circumstances I get 3 more copies of the stack added (not as substacks). This on a

Re: Substacks

On 6/5/22 05:51, General 2018 via use-livecode wrote: Hi, So using real substacks being opened by go to from mainstack and then closing from substack returning to mainstack all working well, thanks for the previous suggestions. Just found some odd behaviour :- The mainstack and substacks

Re: Substacks

Hi, So using real substacks being opened by go to from mainstack and then closing from substack returning to mainstack all working well, thanks for the previous suggestions. Just found some odd behaviour :- The mainstack and substacks have items in PreOpenStack. The substack has for example

Re: Substacks

within standalone settings and it worked fine. Regards Camm > On 29 May 2022, at 17:27, J. Landman Gay via use-livecode > wrote: > > Just to clarify, are they real substacks or do you mean they are separate > stacks that you include in the build? Also, double check that standal

Re: Substacks

Just to clarify, are they real substacks or do you mean they are separate stacks that you include in the build? Also, double check that standalone settings isn't set up to move substacks into separate files. I think that option is in the general pane but I'm not at my compute

Re: Substacks

egards > >>> On 29 May 2022, at 00:12, Mark Wieder via use-livecode >>> wrote: >>> >>> On 5/28/22 07:15, General 2018 via use-livecode wrote: >>> Hi , >>> New to substacks - I have a “mainstack” used as a menu page for 2x >>>

Re: Substacks

:15, General 2018 via use-livecode wrote: >> Hi , >> New to substacks - I have a “mainstack” used as a menu page for 2x >> “substacks” >> When “substacks” opened from “mainstack” they open fine using — go to stack >> “xyz” >> The problem is closing of the “substack

Re: Substacks

On 5/28/22 07:15, General 2018 via use-livecode wrote: Hi , New to substacks - I have a “mainstack” used as a menu page for 2x “substacks” When “substacks” opened from “mainstack” they open fine using — go to stack “xyz” The problem is closing of the “substacks” using - close stack, go to

Re: Substacks

th if called from the mainstack and from the substack. Only the substack >> is closed. >> >> Livecode 9.6.7 and Windows 10 >> >> >> Hope this helps >> >> Thomas >> >> >>>> Am 28.05.2022 um 16:15 schrieb General 2018 via us

Re: Substacks

n the IDE at least, both if called from the mainstack and from the substack. Only the substack is closed. Livecode 9.6.7 and Windows 10 Hope this helps Thomas Am 28.05.2022 um 16:15 schrieb General 2018 via use-livecode: Hi , New to substacks - I have a “mainstack” used as a menu page

Re: Substacks

the IDE at least, > both if called from the mainstack and from the substack. Only the substack is > closed. > > Livecode 9.6.7 and Windows 10 > > > Hope this helps > > Thomas > > >> Am 28.05.2022 um 16:15 schrieb General 2018 via use-livecode: >>

Re: Substacks

ecode: Hi , New to substacks - I have a “mainstack” used as a menu page for 2x “substacks” When “substacks” opened from “mainstack” they open fine using — go to stack “xyz” The problem is closing of the “substacks” using - close stack, go to “mainstack” or close this stack it always closes (quit)

Substacks

Hi , New to substacks - I have a “mainstack” used as a menu page for 2x “substacks” When “substacks” opened from “mainstack” they open fine using — go to stack “xyz” The problem is closing of the “substacks” using - close stack, go to “mainstack” or close this stack it always closes (quit

Re: where does the standalonebuilder saves the substacks in an Mac OS App?

Is it a library that will not be edited programmatically at runtime? If not, then that is the place it belongs. Bob S > On Mar 28, 2017, at 06:07 , Tiemo Hollmann TB via use-livecode > wrote: > > Creating a standalone on MacOS 10.12 with LC 8.1.3, LiveCode puts the file > "revsecurity.dylib

AW: where does the standalonebuilder saves the substacks in an Mac OS App?

hricht- Von: use-livecode [mailto:use-livecode-boun...@lists.runrev.com] Im Auftrag von J. Landman Gay via use-livecode Gesendet: Montag, 27. März 2017 20:31 An: How to use LiveCode Cc: J. Landman Gay Betreff: Re: where does the standalonebuilder saves the substacks in an Mac OS App? I think

Re: where does the standalonebuilder saves the substacks in an Mac OS App?

I think that's right, Apple enforces this rule. The standalone builder will move files to a Resources folder when it builds the app. For backward compatibility, scripts that reference the engine folder are redirected to the Resources folder automatically. On 3/27/17 1:22 PM, Bob Sneidar via u

Re: where does the standalonebuilder saves the substacks in an Mac OS App?

To my understanding, it's a requirement in accordance with Apple's sandboxing policies, if you want an executable to be able to make changes to files inside the executable bundle. The way it's supposed to work, no application is allowed to write or modify anything in the old location where the a

AW: where does the standalonebuilder saves the substacks in an Mac OS App?

ode wrote: > is it correct when the standalone settings of an stack are set to move > substacks into individual stack files that under Mac OS X the > substacks in an compiled app (e.g. test.app) are stored > > in 'test.app/Contents/Resources/_MacOS/‘ instead of being stored in

Re: where does the standalonebuilder saves the substacks in an Mac OS App?

; is it correct when the standalone settings of an stack are set to >> move substacks into individual stack files that under Mac OS X the >> substacks in an compiled app (e.g. test.app) are stored >> >> in 'test.app/Contents/Resources/_MacOS/‘ instead of being stored in >&g

Re: where does the standalonebuilder saves the substacks in an Mac OS App?

On 3/14/17 6:58 PM, Matthias Rebbe via use-livecode wrote: is it correct when the standalone settings of an stack are set to move substacks into individual stack files that under Mac OS X the substacks in an compiled app (e.g. test.app) are stored in 'test.app/Contents/Resources/_

where does the standalonebuilder saves the substacks in an Mac OS App?

Hi, is it correct when the standalone settings of an stack are set to move substacks into individual stack files that under Mac OS X the substacks in an compiled app (e.g. test.app) are stored in 'test.app/Contents/Resources/_MacOS/‘ instead of being stored in 'test.app/Cont

Re: HTML5 "Features" Library Substacks and "send ### in time"

On 07/02/2016 01:59, Sannyasin Brahmanathaswami wrote: Yikes… ! I just read this today… after seeing the newsletter and then looking in the guide in LC 8 dp 14 "The HTML5 engine in this release of LiveCode has a limited range of features. You can: deploy single-stack applications with embed

Re: HTML5 "Features" Library Substacks and "send ### in time"

Ciao, [1] Firefox does NOT work any more since version 44.0 with LC's HTML5-standalones. Sadly, because Firefox was up to 5 times faster with the standalones (with loading AND playing) than other browsers. ALL standalones are affected, no matter the dp version. This is reported at Bugzilla@Mozilla

Re: HTML5 "Features" Library Substacks and "send ### in time"

Hi Brahmanathaswami, I did not have the time to test DP 14 yet, but in DP9 animationEngine worked pretty good (in Firefox). All I had to do was make animationengine a substack of my mainstack. As it relies heaviely on send in time, I can confirm that that used to be working fine at least in DP

HTML5 "Features" Library Substacks and "send ### in time"

  Yikes… ! I just read this today… after seeing the newsletter and then looking in the guide in LC 8 dp 14 "The HTML5 engine in this release of LiveCode has a limited range of features. You can: deploy single-stack applications with embedded resources" BR: Does this mean you cannot include a

Re: copying from password protected substacks

Peter Haworth wrote: > I'm still not sure in my mind whether "encryption" is the same thing > as password protecting a stack. I've only ever used the latter. > Anybody know? AFAIK there is only one form of script encryption, set with the password property and unlocked during the session with t

Re: copying from password protected substacks

Right. I'm still not sure in my mind whether "encryption" is the same thing as password protecting a stack. I've only ever used the latter. Anybody know? Pete lcSQL Software Home of lcStackBrowser and SQLiteAdmin

Re: copying from password protected substacks

You can use this: function expandError pErr -- expands LC runtime error numbers, with explanatory text -- probably based on a handler from someone on the use-LC list, not sure who -- revised by Peter M. Brigham, pmb...@gmail.com — freeware -- requires sr() repeat for each li

Re: copying from password protected substacks

On 4/14/2015 8:26 PM, Peter Haworth wrote: Unless there's a bug somewhere in the decryption routines, it still feels like the passkey you are supplying is not the same one you specified in the standalone settings. That's what it sounds like to me too. I wonder how the standalone builder handle

Re: copying from password protected substacks

On 4/14/2015 8:17 PM, Dr. Hawkins wrote: However, where can I find the list of those codes, and what that error box means in general? User Sample Stacks (in the toolbar) -> LC Error Lookup or here: Or make your own, the locati

Re: copying from password protected substacks

The first item of each line refers to a line number in an error messages table. The table is in the cErrorsList custom property of card 1 of stack revErrorDisplay. Sounds like you set the encrypt with password field in the standalone settings. Make sure you do that for every stack you want to be

Re: copying from password protected substacks

On Tue, Apr 14, 2015 at 2:50 PM, Peter Haworth wrote: > Error 558 is "stack: invalid key". Not much help but perhaps the passkey > you're supplying isn't the correct one? Not likely I guess since it > apparently works in the IDE. > There is no password set in the IDE; it's all at compile time.

Re: copying from password protected substacks

Error 558 is "stack: invalid key". Not much help but perhaps the passkey you're supplying isn't the correct one? Not likely I guess since it apparently works in the IDE. Pete lcSQL Software Home of lcStackBrowser and SQLiteAdmin <

Re: copying from password protected substacks

On Tue, Apr 14, 2015 at 2:09 PM, Scott Rossi wrote: > Does it work for you in the IDE? > Yes. However, the password only gets set at compile time. > Also, you're not using the Community Edition are you? > *shudder*, no. Far too much work into this to risk GPL contamination/taiint of my cod

Re: copying from password protected substacks

Does it work for you in the IDE? Also, you're not using the Community Edition are you? You can't password protect with that version of LiveCode even though it shows the option in the Standalone Builder. Regards, Scott Rossi Creative Director Tactile Media, UX/UI Design On 4/14/15, 1:50 PM,

Re: copying from password protected substacks

On Tue, Apr 14, 2015 at 12:03 PM, Scott Rossi wrote: > There shouldn't be anything infuriating about it. > > You have a password protected stack. You set the passkey of that stack to > your password value. You should then be able to access/copy objects from > that stack. > but that doesn't see

Re: copying from password protected substacks

There shouldn't be anything infuriating about it. You have a password protected stack. You set the passkey of that stack to your password value. You should then be able to access/copy objects from that stack. The passkey stays in effect for the current editing session. When you close stack (or

Re: copying from password protected substacks

On Sat, Apr 11, 2015 at 5:26 PM, Scott Rossi wrote: > If you set the passkey of the protected stack (to the password) before > copying, you should be able to copy what you want > This is getting infuriating . . . what *is* the scope of the passkey? I've tried setting it during stack initializ

Re: copying from password protected substacks

If you set the passkey of the protected stack (to the password) before copying, you should be able to copy what you want. Regards, Scott Rossi Creative Director Tactile Media, UX/UI Design On 4/11/15, 5:10 PM, "Dr. Hawkins" wrote: >Thanks. But this will make life *much* more difficult. Ca

Re: copying from password protected substacks

On Sat, Apr 11, 2015 at 3:59 PM, Mark Schonewille < m.schonewi...@economy-x-talk.com> wrote: > You can't copy controls from password protected stacks, because that would > allow you to paste controls on unprotected stacks and read the scripts. > Thanks. But this will make life *much* more diffic

Re: copying from password protected substacks

Hi Richard, You can't copy controls from password protected stacks, because that would allow you to paste controls on unprotected stacks and read the scripts. The solution is to create controls in an unprotected stack without scripts and set the parentScript of these controls to a button wit

Re: copying from password protected substacks

On Sat, Apr 11, 2015 at 3:52 PM, Dr. Hawkins wrote: > have found that when I try to copy a group from a stack that I clone > (turns out to be much faster to add objects to that group and delete the > group than to delete individual items), I get a "can't cut object. Also, a

copying from password protected substacks

I absolutely need my source stacks encrypted. I have found that when I try to copy a group from a stack that I clone (turns out to be much faster to add objects to that group and delete the group than to delete individual items), I get a "can't cut object. Stack is password protected" error in t

Re: scope of gRevAppIcon on substacks

Look under "icon." You're loading the global, and then the engine is executing the equivalent of: global gRevAppIcon set the icon of button xxx of stack "Answer Dialog" to gRevAppIcon so the rules for setting icons apply. -- Peter Peter M. Brigham pmb...@gmail.com http://home.comcast.net/~

Re: scope of gRevAppIcon on substacks

On Fri, Mar 6, 2015 at 7:58 PM, Peter M. Brigham wrote: > From the dictionary: > > - > LiveCode looks for the specified image in the following order: > Thanks. That and Jacqui's explanation of standalones will probably solve everything (it really doesn't matter whether it gives me the imag

Re: scope of gRevAppIcon on substacks

On 3/6/2015 9:58 PM, Peter M. Brigham wrote: What you DO have to do is call this every time before you invoke an ask or answer dialog. The globals seem to be reset on idle, so they don't stick. It's a PITA that way. In a standalone it sticks and you only need to set it up once. It's just the I

Re: scope of gRevAppIcon on substacks

B) The object's stack's mainstack (if a substack) C) The object's stack's mainstacks substacks D) The list of open stacks, in order they were loaded - What you DO have to do is call this every time before you invoke an ask or answer dialog. The globals seem to be rese

scope of gRevAppIcon on substacks

I'm trying (finally) to use gRevAppIcon, which displays an icon in ask & answer. It seems that this uses the *short* id of the image, which would seem to limit it to the stack in which it occurs (or possibly to the main stack). I've set it as a global in my mainstack, and it is used in the test a

Re: Best Practice: Prevent Substacks from Triggering Main Stack Scripts

On Fri, Feb 6, 2015 at 12:33 PM, J. Landman Gay wrote: > If almost everything needs to use the open* handlers except one or two > stacks, then I put the handlers into the mainstack stack script and put > blocking handlers into the stacks that are an exception. This. I quickly figured out that

Re: Best Practice: Prevent Substacks from Triggering Main Stack Scripts

Richard Gaskin wrote: 1) If the mainstack is a single card, just put the handler in the card script. 2) If the mainstack has multiple cards, put the handler in a common group script. 3) If neither of those are viable in your setup, you could add a check to make sure the long name of "me"

Re: Best Practice: Prevent Substacks from Triggering Main Stack Scripts

Brahmanathaswami wrote: "it depends" got it... for me it's not about protecting anything.. it's about..eg. on resizestack x,y set the rect of some grc to the rect of this card # and other tricks here relating to dynamic geometry changes... end resize stack This gets triggered by a substa

Re: Best Practice: Prevent Substacks from Triggering Main Stack Scripts

"it depends" got it... for me it's not about protecting anything.. it's about..eg. on resizestack x,y set the rect of some grc to the rect of this card # and other tricks here relating to dynamic geometry changes... end resize stack This gets triggered by a substack that does not have tho

Re: Best Practice: Prevent Substacks from Triggering Main Stack Scripts

On 2/6/2015 12:49 AM, Brahmanathaswami wrote: If you put any preopenstack, resizestack, close stack etc. script in the mainstack script.. these will be triggered by the same action in a substack. What is the best way to avoid this? I usually do the thing where you put the open* handlers into t

Re: Best Practice: Prevent Substacks from Triggering Main Stack Scripts

On 2/6/2015 1:38 PM, Bob Sneidar wrote: Not sure but if you password protect the main stack, aren’t the substacks inaccessible as well? Nope. You have to protect each one separately. -- Jacqueline Landman Gay | jac...@hyperactivesw.com HyperActive Software | http

Re: Best Practice: Prevent Substacks from Triggering Main Stack Scripts

There are some advantages to using substacks methinks. The monistic automatically “knows” about the substacks without any extra coding or adding the stacks to the main stack files property. Also, I am not sure that graphics loaded in the main stack will be accessible to any stacks that are not

Re: Best Practice: Prevent Substacks from Triggering Main Stack Scripts

Put the handlers in the card script of the main stack. When opening the mainStack the card will receive the messages, but not when the substacks are opened. The card of the mainStack is not in the message path of the substacks. Alternately, you can put the same handlers in the substacks stack

Re: Best Practice: Prevent Substacks from Triggering Main Stack Scripts

Hi Brahmanathaswami, It isn't obligatory to use substacks. You could use two mainstacks simultaneously. Just make sure to include the additional mainstacks as files when you build a standalone. With two mainstacks, the scripts in one stack won't be triggered by messages from the

Re: Best Practice: Prevent Substacks from Triggering Main Stack Scripts

If you can do it, the easiest way is to place all your handlers in the card script of the first card of your main stack. All the handlers will be triggered by the main stack, but not the substacks. If you must place your handlers in the stack script, you can compare the name of the owner of

Best Practice: Prevent Substacks from Triggering Main Stack Scripts

that architecture. I'm so use to running most script in the main stack script for simplicity sake and ease of finding things. I suppose one can install "dummy" handlers in the substacks to match. e.g on preopenstack end preopenstack and since you are not passing anything, I sus

Re: TemplateStacks or SubStacks, Which is better?

Hi Cal, The templateStack is something that only exists in memory. A templateStack is only displayed when you make a new stack. A substack can exist both in memory and on disk and you don't need to make a new stack to display it. What you will use, depends on what you want to do. Perhaps you

TemplateStacks or SubStacks, Which is better?

There comes a time in the use of LiveCode when you run across the concept of a template stack or a substack as a entry/data display form. The questions that you might be faced with are: Which one should you use? Which is the most efficient as a form(date entry) etc.? How much memory does each typ

excluding substacks from standalone build

I had thought that there was an option to determine which substacks got built into a standalone. Was I mistake? So if I have substacks that are only used for development, and not by users do I do something like shell copy thisstack.livecode to buildme.livecode send prepareyourself to stack

Re: sharing menus among substacks

awkins wrote: > Some time ago, I went through the hassle of making menus, and copying them > between my substacks. > > Is there *any* way to simply have a single menu set that stays in sync > among substacks, rather then needing to copy to every

Re: sharing menus among substacks

On 3/2/13 9:24 PM, Dr. Hawkins wrote: Some time ago, I went through the hassle of making menus, and copying them between my substacks. Is there *any* way to simply have a single menu set that stays in sync among substacks, rather then needing to copy to every substack every time??? Set the

sharing menus among substacks

Some time ago, I went through the hassle of making menus, and copying them between my substacks. Is there *any* way to simply have a single menu set that stays in sync among substacks, rather then needing to copy to every substack every time??? ___ use

Re: omitting substacks from standalone

: > > > > If this isn't what you want, I'd suggest you explain a little more about > what you're > > trying to accomplish. > > I have a few "operative" substacks, but I also have an administrative > substack that sets things in the other stack

Re: omitting substacks from standalone

On Fri, Aug 17, 2012 at 2:14 PM, Mark Schonewille wrote: > > If this isn't what you want, I'd suggest you explain a little more about what > you're > trying to accomplish. I have a few "operative" substacks, but I also have an administrative substack that

Re: omitting substacks from standalone

Hi Richard, I don't understand why you would want that. You make a project either with or without substacks and if you decide you don't want substacks anymore then you just delete them. If you want your substacks to be in separate files, you can check an option in the standalone a

omitting substacks from standalone

I'm looking through the options, and can't find a way to do it. Is there a way to omit substacks from the standalone when I build it? Or do I need to build a script to duplicate the stack modify that stack, and build a standalone for it? Thanks -- The Hawkins Law Firm Richard E. Ha

Saving to substacks in standalones

Hi all. I've been reading recent discussions here about saving substacks in standalones and have a few followup questions. Here's the plan: The app is for Mac/Win/iOS and will use a stub (splashscreen) as the main stack. I'll put the app logic code in a substack and use anothe

Re: jumping among Mainstack and substacks isn't easy

The mouseup message accepts one parameter, which is the number of the button pressed, normally 1 (left-click) or 3 (right-click). You can't pass other info along with the message, you have to build up your data inside the handler, as you in fact do with the stuff below that works. On Jun 19, 20

Re: jumping among Mainstack and substacks isn't easy

Don't put the quotes around the name in tUsername. Pete lcSQL Software On Tue, Jun 19, 2012 at 11:04 AM, Mark Rauterkus wrote: > Hi, > > Still here with newbie frustration and needing to move along. > > So, > > This works for me in a button. > > on mouseUp tUserName

Re: jumping among Mainstack and substacks isn't easy

Mark, You don't need to include the quotes in your card name. The way you're doing it the name is literally: "Roberto Clemente" So in effect you are asking LC to go to a card with the name that *includes* the quotes. Just leave out the quote constants: put tFirstName & space & tSecondNa

Re: jumping among Mainstack and substacks isn't easy

Hi, Still here with newbie frustration and needing to move along. So, This works for me in a button. on mouseUp tUserName put "Roberto Clemente" into tUserName put "Present on" && the short english date & return after field "Attendance" of card tUserName of stack "Kids" end mouseUp

Re: jumping among Mainstack and substacks isn't easy

The debugger is your friend here. Insert a breakpoint and then step through your code to see what your variables *really* contain. If your variable is "Roberte Clemente of stack Kids", then in the words of an old and wise farmer, "You can't get there from here". You are saying that there is a ca

Re: jumping among Mainstack and substacks isn't easy

On 6/18/12 9:05 PM, Mark Rauterkus wrote: Hi Again, I can't build a script that crafts a temp variable that can be used in a "go to card name" script. #Fail for me. So, I want to go to a different stack. -- check. write to a field -- check But I can't get to the proper card. I put the card n

Re: jumping among Mainstack and substacks isn't easy

Hi Again, I can't build a script that crafts a temp variable that can be used in a "go to card name" script. #Fail for me. So, I want to go to a different stack. -- check. write to a field -- check But I can't get to the proper card. I put the card name into that vTempC temp handle, complete w

Re: jumping among Mainstack and substacks isn't easy

On 18.06.2012 at 14:34 Uhr -0700 Bob Sneidar apparently wrote: hmmm... If by context you mean that if I go to a card in another stack and get the name of this card, it will return the name of the card I came from and not the card I went to, I think you are mistaken, but I may have misunderstoo

Re: jumping among Mainstack and substacks isn't easy

On Jun 18, 2012, at 2:16 PM, Robert Brenstein wrote: > On 18.06.2012 at 12:03 Uhr -0700 Bob Sneidar apparently wrote: >> I'm not entirely sure this is the issue, but let me describe how Livecode >> interprets your code. When you say "field boy", Livecode translates that to >> "field "boy" of th

Re: jumping among Mainstack and substacks isn't easy

On 18.06.2012 at 12:03 Uhr -0700 Bob Sneidar apparently wrote: I'm not entirely sure this is the issue, but let me describe how Livecode interprets your code. When you say "field boy", Livecode translates that to "field "boy" of the current card of the topstack" (others will correct me if I am

Re: jumping among Mainstack and substacks isn't easy

On 18.06.2012 at 16:36 Uhr -0400 Mark Rauterkus apparently wrote: Hi, Yep. LC just went strict with me. Errors such as: stack "Kids": compilation error at line 4 (Expression: unquoted literal), char 46 For the past week or two I've been FINE without these issues. Seemed as if LC didn't care. N

Re: jumping among Mainstack and substacks isn't easy

I do not see how the second form has any meaning. vTempC will be the number of the mouse button you clicked. Bob On Jun 18, 2012, at 1:36 PM, Mark Rauterkus wrote: > This works: > > on mouseUp > go to card "Roberto Clemente" of stack "Kids" > end mouseUp > > But, this does not: > > on mo

Re: jumping among Mainstack and substacks isn't easy

Hi, Yep. LC just went strict with me. Errors such as: stack "Kids": compilation error at line 4 (Expression: unquoted literal), char 46 For the past week or two I've been FINE without these issues. Seemed as if LC didn't care. Now I've gone back throughout the code looking at the colors of the w

Re: jumping among Mainstack and substacks isn't easy

at 11:12 AM, Mark Rauterkus wrote: > Hi, > > My database for camper kids is progressing, but some newbie head > scratching is in full force. > > Cards in a mainstack keep contact info and attendance details, one > card per person. This seems to be working fine, except when

jumping among Mainstack and substacks isn't easy

Hi, My database for camper kids is progressing, but some newbie head scratching is in full force. Cards in a mainstack keep contact info and attendance details, one card per person. This seems to be working fine, except when I jump to different substacks. Then an error occurs. Case in point: I

Re: Time-Stamping Demo programs via substacks?

In the clouds, baby! That presupposes that my target demographic are all connected, permanently, to the internet; and they are not. Richmond, The best way to go is to call the DAZE30 function from your standalone and compare it with a TSTAMP reference stored on the cloud so your customers w

Re: Time-Stamping Demo programs via substacks?

Richmond, The best way to go is to call the DAZE30 function from your standalone and compare it with a TSTAMP reference stored on the cloud so your customers won't find any local file to delete to get a way to bypass your 30 days try-period key. HTH, Le 23 avr. 2012 à 10:31, Richmond a écrit

Time-Stamping Demo programs via substacks?

Um: --30 Day code-- if the fld "STAMP" of stack "STAMP" is empty then set the lockScreen to true put the seconds into into fld "STAMP" of stack "STAMP" save stack "STAMP" set the lockScreen to false end if put the seconds into DAZE30 put fld "STAMP" of stack "STAMP" into TSTAMP if D

Re: Confused about substacks

braries etc included. Then you can have your real stack with its > substacks be opened by the splash. As long as the right support stuff is > included the splash you can "go stack.." and it should be fine, and the > splashstack can handle the saving of changes to your real stack. &

Re: Confused about substacks

Probably what will work is to make a stackrunner type of splash stack with any libraries etc included. Then you can have your real stack with its substacks be opened by the splash. As long as the right support stuff is included the splash you can "go stack.." and it should be fin

Re: Confused about substacks

file containing the mainstack. In effect >> the stackfile containing the former mainstack is "orphaned". Usually I just >> get rid of these orphaned stackfiles to avoid confusion. >> >> Bottom line: substacks are part of the same stack file of the mainstack. >>

Re: Confused about substacks

e containing the mainstack. In effect the > stackfile containing the former mainstack is "orphaned". Usually I just get > rid of these orphaned stackfiles to avoid confusion. > > Bottom line: substacks are part of the same stack file of the mainstack. > > Hope

Re: Confused about substacks

Oic. Because if they are substacks of the splash stack then they are part of the standalone and therefore not editable. That makes sense. I think I am misusing substacks then. I should just make them individual stacks on the hard drive. The goal is to have multiple editable forms open at the

Re: Confused about substacks

Assuming you are doing this so that you can save your stack file, yes. When you make a stack a substack, I do believe it incorporates it all together. However, there is a setting in the standalone builder that avoids this when you build a standalone. Its under the stacks heading, "move subs

Re: Confused about substacks

. Bottom line: substacks are part of the same stack file of the mainstack. Hope this it what you were asking. Devin On Nov 18, 2011, at 4:36 PM, Bob Sneidar wrote: > Hi all. > > I am a bit confused now. I created a new stack, saved it, made it a substack > of my splash stack.

Confused about substacks

Hi all. I am a bit confused now. I created a new stack, saved it, made it a substack of my splash stack. No problemo. I can see the substack on the hard drive, I can see the substack in the application browser as a substack of my splash stack. BUT THEN... I right clicked my splash stack in t

Re: SubStacks and message path

mulate popping a substack with a fancy window shape) instead of unnecessary substacks! I think I'm gradually learning how to avoid the bits of LiveCode that I don't understand enough to be able to control! ;-) Best, Keith.. On 5 Jun 2011, at 17:00, Robert Brenstein wrote: > I think th

Re: SubStacks and message path

hould place the SOAP substack into the message path library 'slot' for the MainStack and any other substacks (such as this login one). So, maybe I just had a typo somewhere - that wouldn't be a first! Best, Keith.. I think that your problem with original scenerio was not with pat

Re: SubStacks and message path

'slot' for the MainStack and any other substacks (such as this login one). So, maybe I just had a typo somewhere - that wouldn't be a first! Best, Keith.. On 4 Jun 2011, at 12:22, Jim Ault wrote: >> On 4 Jun 2011, at 09:07, Keith Clarke wrote: >> >>> Hi folks, >&

Re: SubStacks and message path

e one-liner in the 'on openstack' of the SOAP stack script. start using stack (the short name of me) If you do this in the main stack, then use start using stack "SOAP functions" -- this puts only the stack script into the 'library' part of the message pa

  1   2   >