Save/Open stack to/from variable?

In a situation where you can't 'directly' access the filesystem in order to save or read a stack but can write any variable to a local file and read from any local file to a variable, the questions arise: • Can we save (the current state of) a stack to a variable in a format as the usual

Re: Make an open stack modal by script

Ah, yes - the *property* is read-only; I had mistakenly read that as being about the stack itself somehow being read-only. Yes, the relationship between mode, style, and the mode commands (toplevel, palette, modal, modeless) are wonderfully flexible. Mode lets us know what state the window

Re: Make an open stack modal by script

The Property called mode is read only. The mode is set using the style keyword as was pointed out. That works a peach! I had been jumping through hoops to prevent users from accidentally switching a customer or site while editing a device record belonging to one of those two. Now I just set the

Re: Make an open stack modal by script

Bob Sneidar wrote: > Unfortunately, and to my great chagrin, the mode of a window is read > only. What does that mean? What exactly do you see? I can't think of any mode that prevents text entry, so maybe you've encountered a bug, or some other script is preventing editing. -- Richard

Re: Make an open stack modal by script

Brilliant! This will make things much smoother. I was hiding all other substacks while editing, but the disappearance of the other windows was disconcerting. Bob S > On Mar 28, 2018, at 08:50 , Paul Dupuis via use-livecode > wrote: > > set the style of stack

Re: Make an open stack modal by script

set the style of stack XXX to modal set the tail end of the style entry in the Dictionary for details On 3/28/2018 11:35 AM, Bob Sneidar via use-livecode wrote: > Hi all. > > I broached this subject before but in the reverse direction. I have an app > that allows multiple windows (I call

Make an open stack modal by script

Hi all. I broached this subject before but in the reverse direction. I have an app that allows multiple windows (I call forms) open at the same time. For instance I can have the customer form, the sites form and the devices form open simultaneously. Changing the customer loads the sites for

Re: Open stack "MyStack" Not working

mpany. Roger > On Jan 29, 2018, at 2:57 PM, Kay C Lan via use-livecode > <use-livecode@lists.runrev.com> wrote: > > What is the line before your "open stack" line? > Is there any chance that the stack "myStack" has accidently had it's > name changed:

Re: Open stack "MyStack" Not working

What is the line before your "open stack" line? Is there any chance that the stack "myStack" has accidently had it's name changed: " myStack", "myStack ", " myStack " or "my Stack" - note the spaces What happens when you enter the command

Open stack "MyStack" Not working

All of a sudden, today, open stack “myStack” Does not work. I results in this error: Message execution error: Error description: Handler: error in statement Hint: message So far, I’ve tried restarting my Mac (OS 10.13.2) a number of times and I’ve tried ditching the prefs, all to no avail

Placing a group on topleft of open stack

Hi All, In a recent forum thread: http://forums.livecode.com/viewtopic.php?f=53=29207 there is a stack that lists all livecode stacks within a folder. The user just have to click the stack's name to open. Now, I am trying to add a group on topleft of every open stack (A group with 4 buttons

Re: open stack

, instead of just "there was an error." Anywho, I'm trying to add a dictionary entry for "open stack" with an example of setting the defaultFolder first. On Wed, Aug 24, 2016 at 3:11 PM, Mike Bonner <bonnm...@gmail.com> wrote: > If you're working in the ide, chances are

Re: open stack

If you're working in the ide, chances are the defaultfolder is not set to point to the correct place, which would mean you'd need to provide a full path to the stack you want to open, or set the default folder to point to the right place. the line "if there is a stack tFilename then open

open stack

What's up with this not working? http://lessons.livecode.com/m/4071/l/17375-how-do-i-save-custom-properties-in-a-standalone-application This is a really simple tutorial that I followed, but I get an error at the "open stack" statement. I tried replacing it with this, but even though

Re: When is open stack sent on Mobile

Make sense, the dictionary doesn't state explicitly that a resizeStack msg is sent when orientation is changed.. that's why I did not go that route, but looking at the orientationChanged entry… which says " If you wish to perform an action after the interface has been rotated, then

Re: When is open stack sent on Mobile

On 7/28/2016 12:46 PM, Sannyasin Brahmanathaswami wrote: switching from landscape to portrait -- similarly one must re-set up the UI explicitly and typically the old way of doing such would be in a preopen or open stack handlers… again, these need to fire when moving back and forth. Just

Re: When is open stack sent on Mobile

Sannyasin Brahmanathaswami wrote: > switching from landscape to portrait > -- similarly one must re-set up the UI explicitly and typically > the old way of doing such would be in a preopen or open stack > handlers… I've been handling stack resizing with a resizeStack h

Re: When is open stack sent on Mobile

required on any given card will differ. So if you are firing those on open stack, then you need to close it first. I'm a newbie at this mobile stuff, so perhaps over time we will find better architecture, but for now I've start issuing a "close this stack" on every move to a diffe

Re: When is open stack sent on Mobile

On 2016-07-28 01:25, Sannyasin Brahmanathaswami wrote: It appears on mobile you can issue go stack "stackOne" and then later go stack "stackTwo" and then you will only see "stackOne" But if you have links that go backto "stackOne" I'm not gett

Re: When is open stack sent on Mobile

What kind of Mickey Mouse operation is this anyway?! On Thu, Jul 28, 2016 at 11:13 AM, Richard Gaskin wrote: > Sannyasin Brahmanathaswami wrote: > > > Anyone doing Android? > > Only 80% of smartphone users, 70% of tablet users, and now 100& of current > Chromebook

Re: When is open stack sent on Mobile

Sannyasin Brahmanathaswami wrote: > Anyone doing Android? Only 80% of smartphone users, 70% of tablet users, and now 100& of current Chromebook users too. :) > can you check to see if Suspend and Resume are passed to stacks > that come and go from the foreground of the app? (but are not >

Re: When is open stack sent on Mobile

@ Paul: tks OK I'll test for that… the dictionary is behind for many entries… so perhaps this is one of them. Anyone doing Android? can you check to see if Suspend and Resume are passed to stacks that come and go from the foreground of the app? (but are not closed along the way..) BR On

Re: When is open stack sent on Mobile

sin Brahmanathaswami <bra...@hindu.org> > wrote: > > It appears on mobile you can issue > > go stack "stackOne" > > and then later > > go stack "stackTwo" > > and then you will only see "stackOne" > > But if you have l

When is open stack sent on Mobile

It appears on mobile you can issue go stack "stackOne" and then later go stack "stackTwo" and then you will only see "stackOne" But if you have links that go backto "stackOne" I'm not getting any open stack or open card messages handlers to fire.

Re: Default tool on open stack

On 2016-04-20 17:09, Bob Sneidar wrote: I get an error with these. V 6.7.6 They are specific to the version 8 IDE - which is why. Warmest Regards, Mark. -- Mark Waddingham ~ m...@livecode.com ~ http://www.livecode.com/ LiveCode: Everyone can create apps

Re: Default tool on open stack

I get an error with these. V 6.7.6 Bob S On Apr 12, 2016, at 11:35 , Mark Waddingham > wrote: That being said, there are two IDE library APIs which handle the tool switch without going behind the IDE's back: revIDEChooseBrowseTool

Re: Default tool on open stack

Aha! That makes sense. The IDE is un-doing the command... OK, not a bug -- just a quirk. ;-) Tim Selander Tokyo, Japan On 16/04/13 1:13, J. Landman Gay wrote: On April 12, 2016 8:27:15 AM Tim Selander wrote: However, after reading some of the various other comments,

Re: Default tool on open stack

On 2016-04-12 15:25, Tim Selander wrote: Hi again, Basically, my problem is solved with Peter's work-around. However, after reading some of the various other comments, including Jacqueline's here, it strikes me that this has to be considered some kind of bug, doesn't it? Maybe :) It is

Re: Default tool on open stack

On April 12, 2016 8:27:15 AM Tim Selander wrote: However, after reading some of the various other comments, including Jacqueline's here, it strikes me that this has to be considered some kind of bug, doesn't it? A valid command (choose browse tool) in a valid handler

Re: Default tool on open stack

For choosing a default tool I use to use Jacqueline's and other's delayed version. on preopenstack -- whatever here send "choose browse tool" to me in 1 tick -- default end preopenstack -- View this message in context: http://runtime-revolution.278305.n4.nabble.com/Default-to

Re: Default tool on open stack

Peter M. Brigham wrote: > On Apr 12, 2016, at 8:02 AM, Mark Waddingham wrote: > >> A potentially better solution (which insulates them entirely from >> changing tools!) would be to either send your tools to your >> colleagues as plugins (which they put in the My LiveCode/Plugins >> folder), or

Re: Default tool on open stack

Hi again, Basically, my problem is solved with Peter's work-around. However, after reading some of the various other comments, including Jacqueline's here, it strikes me that this has to be considered some kind of bug, doesn't it? A valid command (choose browse tool) in a valid handler

Re: Default tool on open stack

On Apr 12, 2016, at 8:02 AM, Mark Waddingham wrote: > On 2016-04-12 07:07, Tim Selander wrote: >> Hi! >> That worked! Many thanks, Peter. >> Though I agree with Roger, the default tool should be a preference somewhere. >> I'm making little utilities to use at work, and the staff that use >> them

Re: Default tool on open stack

On 2016-04-12 07:07, Tim Selander wrote: Hi! That worked! Many thanks, Peter. Though I agree with Roger, the default tool should be a preference somewhere. I'm making little utilities to use at work, and the staff that use them are always befuddled when they try to click a field to enter

Re: Default tool on open stack

On 4/12/2016 12:39 AM, Mark Wieder wrote: On 04/11/2016 10:07 PM, Tim Selander wrote: Though I agree with Roger, the default tool should be a preference somewhere. I remember suggesting that to Kevin a dozen years ago. I remember at least three speakers at a conference way back who

Re: Default tool on open stack

On 04/11/2016 10:07 PM, Tim Selander wrote: Though I agree with Roger, the default tool should be a preference somewhere. I remember suggesting that to Kevin a dozen years ago. -- Mark Wieder ahsoftw...@gmail.com ___ use-livecode mailing list

Re: Default tool on open stack

Hi! That worked! Many thanks, Peter. Though I agree with Roger, the default tool should be a preference somewhere. I'm making little utilities to use at work, and the staff that use them are always befuddled when they try to click a field to enter text, but the whole field gets selected

Re: Default tool on open stack

This would explain why it worked for me in some cases but not others as well. Another mystery bites the dust! Roger > On Apr 11, 2016, at 8:46 PM, Peter Bogdanoff wrote: > > I should have pointed out that, in my case, the openStack script calls > another handler that

Re: Default tool on open stack

I should have pointed out that, in my case, the openStack script calls another handler that chooses the tool. It must be that delay that allows the choosing to happen. Peter On Apr 11, 2016, at 6:31 PM, Roger Guay wrote: > you’re right again, Jacque. Thanks! > > >> On Apr 11,

Re: Default tool on open stack

you’re right again, Jacque. Thanks! > On Apr 11, 2016, at 5:50 PM, J. Landman Gay wrote: > > It works if you send the instruction a few milliseconds after opencard > finishes. Basically the whole IDE has to be done with its stuff first. > > -- > Jacqueline Landman

Re: Default tool on open stack

It works if you send the instruction a few milliseconds after opencard finishes. Basically the whole IDE has to be done with its stuff first. -- Jacqueline Landman Gay | jac...@hyperactivesw.com HyperActive Software | http://www.hyperactivesw.com On April 11, 2016

Re: Default tool on open stack

That does not work for me in v 7.1.2 but I wish it did!! I think this should be a LC Preference setting. Roger > On Apr 11, 2016, at 4:23 PM, Peter Bogdanoff wrote: > > What I do is—in the openStack handler I place: > > if the environment is "development" then >

Re: Default tool on open stack

What I do is—in the openStack handler I place: if the environment is "development" then choose browse tool end if Seems to be reliable. Peter Bogdanoff UCLA On Apr 11, 2016, at 4:17 PM, Tim Selander wrote: > When I open a stack, in v7 or v8, it always comes up

Default tool on open stack

When I open a stack, in v7 or v8, it always comes up with the Edit Tool chosen. In the openstack handler (stack script) and opencard handler (card script), I have "choose browse tool" but it has no effect. I save the stacks with the browse tool chosen, and quit. Re-open and the Edit tool is

AW: open stack finds stack in wrong path!?

: open stack finds stack in wrong path!? On Jun 15, 2015, at 10:37 AM, Tiemo Hollmann TB toolb...@kestner.de wrote: Hello, LC 6.5.2, OS X 10.9. I have a splash stack and a main stack. The mainStack is located at the regular place on the same level as the executable within the app bundle

Re: open stack finds stack in wrong path!?

On Jun 17, 2015, at 7:55 AM, Tiemo Hollmann TB toolb...@kestner.de wrote: Devin, you were absolutely right, I was using the wrong itemDel :( Thank you for coaching Tiemo That’s right, you would have needed to set the itemDelimiter to slash before the “go to stack” statement. I didn’t

Re: open stack finds stack in wrong path!?

On Jun 16, 2015, at 3:46 AM, Tiemo Hollmann TB toolb...@kestner.de wrote: Hi Devin, thank you for your explanations. Either if I am using *go stack mainStack.rev*, or using the explicite path *go stack item 1 to -2 of the effective filename of this stack slash mainStack.rev* Whatever I

AW: open stack finds stack in wrong path!?

...@lists.runrev.com] Im Auftrag von Devin Asay Gesendet: Montag, 15. Juni 2015 19:59 An: How to use LiveCode Betreff: Re: open stack finds stack in wrong path!? Correction. On Jun 15, 2015, at 11:56 AM, Devin Asay devin_a...@byu.edu wrote: Tiemo, On OS X looking for a stackfile relative

Re: open stack finds stack in wrong path!?

Correction. On Jun 15, 2015, at 11:56 AM, Devin Asay devin_a...@byu.edu wrote: Tiemo, On OS X looking for a stackfile relative to the location of the .app bundle will look inside the .app bundle, as you have seen. This should have said “On OS X looking for a stackfile relative to the

Re: open stack finds stack in wrong path!?

from CD and there also is a windows version on the CD, there is a copy of the mainStack on the same level, as the app bundle in the root of the CD, which is used from the windows exe. On OS X I open the main stack with: open stack (item 1 to -2 of the effective filename of this stack slash

open stack finds stack in wrong path!?

on the same level, as the app bundle in the root of the CD, which is used from the windows exe. On OS X I open the main stack with: open stack (item 1 to -2 of the effective filename of this stack slash mainStack.rev). The splash stack opens correctly the mainStack in its bundle, only as far

Re: Open stack problem

in the answer file dialog, the stack is opened but none of the statements after the open stack command are executed. Just to add to the merriment, if I set a breakpoint on the open stack command, all works fine. I've removed all front scripts but same behavior. Any ideas? Pete lcSQL

Open stack problem

fine if I double click a stack file in the answer file dialog. However if I single click a stack file and then click the Open button in the answer file dialog, the stack is opened but none of the statements after the open stack command are executed. Just to add to the merriment, if I set

Android resize/open stack

Greetings! I am finding something strange about the way LiveCode is working on Android. When a stack opens, the resizeStack message is sent to the stack. This works fine. However, the stack is displayed on the device - THEN it's resized. The same thing happens when you rotate the Android