Save/Open stack to/from variable?

2019-09-01 Thread hh via use-livecode
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 stackfile (may be base64 encoded)?

• Can we open (and set the state of) a stack from a variable that
is in usual stackfile format (may be base64 encoded)?

The "read" question describes an extension of "go stack url" where
the url is a variable in usual stackfile format.

And yes: I don't mean script only stacks.

For example in a HTML5 standalone we have such a situation.
May be also in some mobile standalones(?).
___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode


Re: Make an open stack modal by script

2018-03-29 Thread Richard Gaskin via use-livecode
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 is in at any given time.

Style lets us set a mode as a default when we use open or go.

The mode commands let us override that style to open a stack of any 
style in any mode as needed.


In devolution's DeskView window I use these to allow easy toggling of 
modes by double-clicking the window representation within it:


If that stack's style is toplevel it bring it to the front as toplevel.

If the style is anything else it uses the toplevel command so I can work 
on it.


If its mode is already toplevel but its style is not, it reopens the 
stack in its style.


--
 Richard Gaskin
 Fourth World Systems


Bob Sneidar wrote:

> 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 style to "Modal" while editing and return it to
> "TopLevel" when not.
>
> Bob S
>
>
>> On Mar 28, 2018, at 10:00 , Richard Gaskin wrote:
>>
>> 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 Gaskin

___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode


Re: Make an open stack modal by script

2018-03-28 Thread Bob Sneidar via use-livecode
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 style to 
"Modal" while editing and return it to "TopLevel" when not. 

Bob S


> On Mar 28, 2018, at 10:00 , Richard Gaskin via use-livecode 
>  wrote:
> 
> 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 Gaskin


___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode


Re: Make an open stack modal by script

2018-03-28 Thread Richard Gaskin via use-livecode

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 Gaskin
 Fourth World Systems
 Software Design and Development for the Desktop, Mobile, and the Web
 
 ambassa...@fourthworld.comhttp://www.FourthWorld.com

___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode


Re: Make an open stack modal by script

2018-03-28 Thread Bob Sneidar via use-livecode
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 XXX to modal
> 
> set the tail end of the style entry in the Dictionary for details


___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode


Re: Make an open stack modal by script

2018-03-28 Thread Paul Dupuis via use-livecode
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 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 the new 
> customer and selects the first site, which loads the devices at that site and 
> loads the first device. 
>
> Clearly if I am editing a device, I want to prevent the user from switching 
> the customer or site, pulling the rug out from under the device edit session. 
> A *GREAT* way to do this might be to make the edit window modal when the user 
> enters the edit mode, preventing him from interacting with the other windows 
> until the form data is saved. Unfortunately, and to my great chagrin, the 
> mode of a window is read only. 
>
> Am I going to have to use send in time to close and reopen the window 
> modally, and reverse it when the data is saved? 
>
> Bob S
> ___
> use-livecode mailing list
> use-livecode@lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your subscription 
> preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode
>


___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode


Make an open stack modal by script

2018-03-28 Thread Bob Sneidar via use-livecode
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 the new customer and 
selects the first site, which loads the devices at that site and loads the 
first device. 

Clearly if I am editing a device, I want to prevent the user from switching the 
customer or site, pulling the rug out from under the device edit session. A 
*GREAT* way to do this might be to make the edit window modal when the user 
enters the edit mode, preventing him from interacting with the other windows 
until the form data is saved. Unfortunately, and to my great chagrin, the mode 
of a window is read only. 

Am I going to have to use send in time to close and reopen the window modally, 
and reverse it when the data is saved? 

Bob S
___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode


Re: Open stack "MyStack" Not working

2018-01-29 Thread Roger Guay via use-livecode
Hi Kay C,

Thanks for your help . . . this is really perplexing, but I think I may have 
fixed it. Trouble is, I’m not sure how.

The first thing I did was clean out my LC prefs
Then I deleted and reloaded LC 8.1.8

These two did not seem to fix the problem of not being able to open a stack by 
script, either in the Message Box or in an OpenStack script. So…

I chose to "Save As...” all the stacks that would not open by script with the 
same title and that seems to do it. 

Keeping my fingers crossed and my confusion at bay . . . at least for now

Thanks very much for keeping me company.

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: " myStack", "myStack ", " myStack " or "my Stack" - note
> the spaces
> What happens when you enter the command into the Message Box, does
> that open the Stack? If not, can you use the command to open some
> other Stack? If so, does "myStack" really still exist?
> 
> On Tue, Jan 30, 2018 at 4:56 AM, Roger Guay via use-livecode
> <use-livecode@lists.runrev.com> wrote:
>> 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. I get the same result on LC 
>> 7.1.3, 8.1.7 and 8.1.8.
>> 
>> Any ideas?
>> 
>> Thanks,
>> Roger
>> 
>> 
>> 
>> ___
>> use-livecode mailing list
>> use-livecode@lists.runrev.com
>> Please visit this url to subscribe, unsubscribe and manage your subscription 
>> preferences:
>> http://lists.runrev.com/mailman/listinfo/use-livecode
> 
> ___
> use-livecode mailing list
> use-livecode@lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your subscription 
> preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode

___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: Open stack "MyStack" Not working

2018-01-29 Thread Kay C Lan via use-livecode
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 into the Message Box, does
that open the Stack? If not, can you use the command to open some
other Stack? If so, does "myStack" really still exist?

On Tue, Jan 30, 2018 at 4:56 AM, Roger Guay via use-livecode
<use-livecode@lists.runrev.com> wrote:
> 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. I get the same result on LC 7.1.3, 
> 8.1.7 and 8.1.8.
>
> Any ideas?
>
> Thanks,
> Roger
>
>
>
> ___
> use-livecode mailing list
> use-livecode@lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your subscription 
> preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode

___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Open stack "MyStack" Not working

2018-01-29 Thread Roger Guay via use-livecode
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. I get the same result on LC 7.1.3, 
8.1.7 and 8.1.8.

Any ideas?

Thanks,
Roger



___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Placing a group on topleft of open stack

2017-05-02 Thread Alejandro Tejada via use-livecode
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 to select one of 4 fullscreen modes)
but could not find a way to do this on Android.

How could you place a group on a new stack on Android?

Thanks in advance!

Al
___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode


Re: open stack

2016-08-24 Thread Matt Maier
Ah, yes, thank you. It looks like the defaultFolder must have been wrong.
Manually setting it to the same folder as the stack works.

I'm getting deja vu...like I complained about how the error message should
mention that it failed because it couldn't find the file in the folder
where it looked, 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 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 stack tFilename"  would
> not cause an error. It would either open the stack if it sees it (see the
> sentence above) or do nothing.  If you want to go that route for better
> information, do this..
>
> if there is a stack tfilename then
> open stack tfilename
> else
> answer information "No such stack"
> end if
>
> Alternatively, when you try to open the stack, check to see whats in "it"
> and "the result"  Often one or the other will provide useful information.
>
> On Wed, Aug 24, 2016 at 2:03 AM, Matt Maier <bluebac...@gmail.com> wrote:
>
> > 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 it doesn't error it also
> > doesn't open the "Main Application" stack.
> >
> > if there is a stack tFileName then open stack tFileName
> >
> > I tried replacing it with this, and the try statement does trigger the
> > catch, but there's nothing in the error variable.
> >
> > put "Main Application.livecode" into tFileName
> >try
> >   open stack tFileName
> >catch tError
> >   answer tError
> >end try
> >
> > The go command doesn't work either.
> >
> > Both stacks are in the same folder.
> >
> > The open command isn't even in the dictionary, although it is in the
> online
> > documentation.
> > ___
> > use-livecode mailing list
> > use-livecode@lists.runrev.com
> > Please visit this url to subscribe, unsubscribe and manage your
> > subscription preferences:
> > http://lists.runrev.com/mailman/listinfo/use-livecode
> >
> ___
> use-livecode mailing list
> use-livecode@lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your
> subscription preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode
>
___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode


Re: open stack

2016-08-24 Thread Mike Bonner
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 stack tFilename"  would
not cause an error. It would either open the stack if it sees it (see the
sentence above) or do nothing.  If you want to go that route for better
information, do this..

if there is a stack tfilename then
open stack tfilename
else
answer information "No such stack"
end if

Alternatively, when you try to open the stack, check to see whats in "it"
and "the result"  Often one or the other will provide useful information.

On Wed, Aug 24, 2016 at 2:03 AM, Matt Maier <bluebac...@gmail.com> wrote:

> 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 it doesn't error it also
> doesn't open the "Main Application" stack.
>
> if there is a stack tFileName then open stack tFileName
>
> I tried replacing it with this, and the try statement does trigger the
> catch, but there's nothing in the error variable.
>
> put "Main Application.livecode" into tFileName
>try
>   open stack tFileName
>catch tError
>   answer tError
>end try
>
> The go command doesn't work either.
>
> Both stacks are in the same folder.
>
> The open command isn't even in the dictionary, although it is in the online
> documentation.
> ___
> use-livecode mailing list
> use-livecode@lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your
> subscription preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode
>
___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode


open stack

2016-08-24 Thread Matt Maier
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 it doesn't error it also
doesn't open the "Main Application" stack.

if there is a stack tFileName then open stack tFileName

I tried replacing it with this, and the try statement does trigger the
catch, but there's nothing in the error variable.

put "Main Application.livecode" into tFileName
   try
  open stack tFileName
   catch tError
  answer tError
   end try

The go command doesn't work either.

Both stacks are in the same folder.

The open command isn't even in the dictionary, although it is in the online
documentation.
___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode


Re: When is open stack sent on Mobile

2016-07-28 Thread Sannyasin Brahmanathaswami
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 
either do so on receipt of resizeStack, or by using a send in 0 milliseconds 
command."

it infers that resizeStack is sent.. 

I'll try that.



 

On 7/28/16, 9:05 AM, "use-livecode on behalf of J. Landman Gay" 
 
wrote:

Yeah, what Richard said. Use resizeStack to reset the UI. I think 
specifically setting the rect of the stack may cause issues when you run 
on Android where window sizes are all over the place.

I'd let the engine manage the stack size by using the fullScreenMode 
property, and set up all your objects using relative coords rather than 
hard-coded ones.

___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: When is open stack sent on Mobile

2016-07-28 Thread J. Landman Gay

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 this morning I successfully was able to
go from a stack in portrait orientation lock to portrait, portrait
upside down to a landscape stack, lock to landscape right, left… and
back again…  but it required specifically setting the rect of the
stack to 0,0,414,716 in a preopen stack handler


Yeah, what Richard said. Use resizeStack to reset the UI. I think 
specifically setting the rect of the stack may cause issues when you run 
on Android where window sizes are all over the place.


I'd let the engine manage the stack size by using the fullScreenMode 
property, and set up all your objects using relative coords rather than 
hard-coded ones.


--
Jacqueline Landman Gay | jac...@hyperactivesw.com
HyperActive Software   | http://www.hyperactivesw.com


___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: When is open stack sent on Mobile

2016-07-28 Thread Richard Gaskin

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 handler, sent to 
the card when the stack is first opened on mobile, and on all platforms 
whenever a stack is resized, such as via rotation of the device.


--
 Richard Gaskin
 Fourth World Systems
 Software Design and Development for the Desktop, Mobile, and the Web
 
 ambassa...@fourthworld.comhttp://www.FourthWorld.com

___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: When is open stack sent on Mobile

2016-07-28 Thread Sannyasin Brahmanathaswami
@ Mark… thanks for the clarification

The current app we have in progress is modular… many, many stacks being called 
all of which are independent LC stacks (not substacks of anything). it works 
quite well on the desktop but on mobile there are caveats that have to be dealt 
with explicitly and "immediately" so to speak, when:

instantiating scrollers
 -- the standard implementation is to delete a scrolling regions when 
creating a new one, because you can't necessarily know where (what card, stack) 
the user is coming and going from and the ID and rect of the scroller that is 
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 different "module" (stack) … 
this works. 

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 this morning I successfully was able 
to go from a stack in portrait orientation lock to portrait, portrait upside 
down to a landscape stack, lock to landscape right, left… and back again…  but 
it required specifically setting the rect of the stack to 0,0,414,716 in a 
preopen stack handler

So  I've taken to using things like this throughout, because the user could be 
on card 3 of Stack 2, (portrait) moves to card 5 of Stack 6 (landscape)… so 
"Back" requires

command closeStopCloseGoRecent
   go recent
   close me # to ensure that future preopen and open stack handlers fire
end closeStopCloseGoRecent

so that when we go back to Stack 6.. the 

on preopenstack
   initializeInterfaceDefaults pOrientation 
# in which we explicitly set up card rect
# mobileSetAllowedOrientation  on the fly… 
end preopenstack

I'm sure others could analyze the frame work and come up with more optimized 
methods… but so far it's working!  I'm not sure that "go in window" gets us 
much more than what I'm doing now.

Slowly finding ways to moving thing to common backscripts and behaviors. But 
"who gets the message" can be tricky.  e.g. I'm told that "the script that 
creates mobile object gets it's subsequent messages… " OK… and it appears these 
message will not "cascade up" the message path. So still stuck on scrollers--I 
have the same script to instantiate scrollers in every stack, because the same 
methods that work in that context do not work if I move them to a single common 
behavior for the different stacks… I suspect because the preopencard handler is 
call the 

createScroller "portal-links" 

 and since the messages about this are sent back to the card… the behavior 
never gets it… most significantly, the cmd to delete existing scroller with 
different ID for that same or different region. 

Still wrestling with that one… or rather, threw in the towel after two days 
wasted trying to optimize the architecture.. I bailed and copied that 
createScroller handler to all the stacks… 

learning slowly…


On 7/28/16, 6:43 AM, "use-livecode on behalf of Mark Waddingham" 
<use-livecode-boun...@lists.runrev.com on behalf of m...@livecode.com> wrote:

Stacks on mobile and desktop work in the same way so if you 'go stack' 
then it opens the new stack (if it is not already open) and moves it 
(notionally) to the top (just as happens on desktop - the window of the 
target of 'go' is brought to the front of that layer).

If you use 'go stack ... in window ...' then it will close the current 
stack and open the new one.



___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: When is open stack sent on Mobile

2016-07-28 Thread Mark Waddingham

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 getting any
open stack or open card messages handlers to fire.  I suspect that's
because they are still.

Anyone else using multiple stacks in a mobile app…and found a way to
trap for when a stack does into the background and the comes back into
the foreground (takes over the screen() unfortunately, suspend and
resume, are not available on mobile.


Stacks on mobile and desktop work in the same way so if you 'go stack' 
then it opens the new stack (if it is not already open) and moves it 
(notionally) to the top (just as happens on desktop - the window of the 
target of 'go' is brought to the front of that layer).


If you use 'go stack ... in window ...' then it will close the current 
stack and open the new one.


The suspend / resume messages would be inappropriate here as they are to 
do with switching applications rather than windows (and are not 
currently sent on mobile).


The suspendStack / resumeStack messages are tied to window focus and 
aren't platform specific - they are sent when the stack with input focus 
changes. The fact they apparantly work on iOS and not Android is 
slightly strange, as that mechanism is implemented (on mobile) in the 
platform-independent code so it should work the same way on both. So, 
there is obviously something slightly amiss going on there.


Warmest Regards,

Mark.

--
Mark Waddingham ~ m...@livecode.com ~ http://www.livecode.com/
LiveCode: Everyone can create apps

___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: When is open stack sent on Mobile

2016-07-28 Thread Roger Eller
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 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
> > closed along the way..)
>
> I just tested suspend, resume, suspendStack, and resumeStack - all no-go
> on Android in LC 8.1dp2.
>
> --
>  Richard Gaskin
>  Fourth World Systems
>  Software Design and Development for the Desktop, Mobile, and the Web
>  
>  ambassa...@fourthworld.comhttp://www.FourthWorld.com
>
> ___
> use-livecode mailing list
> use-livecode@lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your
> subscription preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode
>
___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode


Re: When is open stack sent on Mobile

2016-07-28 Thread Richard Gaskin

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
> closed along the way..)

I just tested suspend, resume, suspendStack, and resumeStack - all no-go 
on Android in LC 8.1dp2.


--
 Richard Gaskin
 Fourth World Systems
 Software Design and Development for the Desktop, Mobile, and the Web
 
 ambassa...@fourthworld.comhttp://www.FourthWorld.com

___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode


Re: When is open stack sent on Mobile

2016-07-28 Thread Sannyasin Brahmanathaswami
@ 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 7/27/16, 6:05 PM, "use-livecode on behalf of Paul Hibbert" 
 wrote:

A quick test shows that suspendStack and resumeStack do appear to work on 
the iOS simulator despite the omission of mobile platforms in the dictionary. 
Sorry I don’t have Android set up for testing right now.



___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: When is open stack sent on Mobile

2016-07-27 Thread Paul Hibbert
A quick test shows that suspendStack and resumeStack do appear to work on the 
iOS simulator despite the omission of mobile platforms in the dictionary. Sorry 
I don’t have Android set up for testing right now.

LC 8.1.0 • Mac OSX 10.11.6 • iOS 9.3

Paul

> On Jul 27, 2016, at 4:25 PM, Sannyasin 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 links that go backto "stackOne"  I'm not getting any open 
> stack or open card messages handlers to fire.  I suspect that's because they 
> are still.
> 
> Anyone else using multiple stacks in a mobile app…and found a way to trap for 
> when a stack does into the background and the comes back into the foreground 
> (takes over the screen() unfortunately, suspend and resume, are not available 
> on mobile.
> 
> 
> BR
> ___
> use-livecode mailing list
> use-livecode@lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your subscription 
> preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode


___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

When is open stack sent on Mobile

2016-07-27 Thread Sannyasin Brahmanathaswami
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.  I suspect that's because they are 
still.

Anyone else using multiple stacks in a mobile app…and found a way to trap for 
when a stack does into the background and the comes back into the foreground 
(takes over the screen() unfortunately, suspend and resume, are not available 
on mobile.


BR
___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: Default tool on open stack

2016-04-20 Thread Mark Waddingham

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

___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode


Re: Default tool on open stack

2016-04-20 Thread Bob Sneidar
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
   revIDEChoosePointerTool

___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode


Re: Default tool on open stack

2016-04-12 Thread Tim Selander

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,
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
(openstack) does not work!?


I'm not sure it's actually a bug. The command does work, but the IDE
chooses the edit tool late in its startup sequence, which undoes the
earlier command.

--
Jacqueline Landman Gay | jac...@hyperactivesw.com
HyperActive Software   | http://www.hyperactivesw.com



___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your
subscription preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode



___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode


Re: Default tool on open stack

2016-04-12 Thread Mark Waddingham

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 always important to remember that the IDE uses many of the same 
'meta-level' editing features the engine provides as user stacks do. Due 
to this, it defaults to assuming that (unless explicitly marked as such 
- as suggested in my previous post) any user stack loaded into it is 
wanting to be edited.


I do think that if you are providing tools to use in the IDE for others, 
then it is better to follow its requirements in that regard (e.g. via 
the style property or via being a plugin) than switching the tool in 
user code which will (with the way the engine / IDE currently works) 
always cause some conflict at some point.


That being said, there are two IDE library APIs which handle the tool 
switch without going behind the IDE's back:


revIDEChooseBrowseTool
revIDEChoosePointerTool

Using either of these in a preOpenStack/openStack handler does appear to 
make the setting stick.


Warmest Regards,

Mark.

--
Mark Waddingham ~ m...@livecode.com ~ http://www.livecode.com/
LiveCode: Everyone can create apps

___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode


Re: Default tool on open stack

2016-04-12 Thread J. Landman Gay

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
(openstack) does not work!?


I'm not sure it's actually a bug. The command does work, but the IDE 
chooses the edit tool late in its startup sequence, which undoes the 
earlier command.


--
Jacqueline Landman Gay | jac...@hyperactivesw.com
HyperActive Software   | http://www.hyperactivesw.com



___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode


Re: Default tool on open stack

2016-04-12 Thread -hh
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-tool-on-open-stack-tp4703304p4703356.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 to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode


Re: Default tool on open stack

2016-04-12 Thread Richard Gaskin

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 send them to them after setting the 'style' property
>> of your tool stacks to "modeless". (In the latter case you can set
>> the style back to "topLevel" to edit).
>>
>> In either case, the stacks will load into the IDE permanently in
>> browse mode.
>
> That takes care of Tim's situation, but the general case of
> defaulting to the pointer tool is still an annoyance. If LC is not
> already running and I double-click on a stack to open it, then after
> the IDE loads and then my stack loads I get the pointer tool. Luckily
> I locloc all my buttons and fields or I'd be moving things around
> inadvertently until I remember I have to change to browse mode. I
> would love to be able to change this behavior in LC preferences.

The pointer tool is great for doing layout, but for many layout is not 
where the majority of time is spent in the IDE.  We make an object once, 
and occasionally adjust its properties, but for myself and a good many 
others I know the majority of our time spent in the IDE is scripting, 
and that most often means using the Browse tool.


But rather than wait for LC to consider adding a preference for the 
default tool, I took care of it in my devolution plugin with one line:


   send "choose browse tool" to me in 10 millisecs

I've found even brief timers for boot operations useful because the IDE 
has a very complex load sequence, and a timer helps ensure that 
everything it's doing will settle down before my action is invoked.


There are many other prefs in devolution for tailoring the environment, 
like hiding the Tools palette (for the same reason: I'm not adding 
objects every time I launch the IDE), and even hiding the menu bar 
itself (with devolution I rarely interact with the LC menu bar directly, 
saving good screen space at the top where my projects need it) - feel 
free to borrow any of those boot actions you find useful in your 
projects (though they're easy enough to script it's probably simpler to 
just write them from scratch than to modify devo's more specialized code):



IMO one of the best things about LC is that its IDE is made entirely in 
LC.  Everything is customizable.


What Bill Appleton once said about SuperCard applies perhaps even more 
to LiveCode:


HyperCard is a multimedia authoring environment.  SuperCard is
a tool you can use to make multimedia authoring environments.

--
 Richard Gaskin
 Fourth World Systems
 Software Design and Development for the Desktop, Mobile, and the Web
 
 ambassa...@fourthworld.comhttp://www.FourthWorld.com


___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode


Re: Default tool on open stack

2016-04-12 Thread Tim Selander

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 
(openstack) does not work!?


Tim Selander
Tokyo, Japan

On 2016/04/12, 9:50, 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 Gay | jac...@hyperactivesw.com
HyperActive Software   | http://www.hyperactivesw.com



On April 11, 2016 6:43:23 PM Roger Guay  wrote:


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
 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 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 active.

Why???

Any help appreciated.

Tim Selander
Tokyo, Japan

___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage
your subscription preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode



___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage
your subscription preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode


___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your
subscription preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode




___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your
subscription preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode



___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: Default tool on open stack

2016-04-12 Thread Peter M. Brigham
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 are always befuddled when they try to click a field to enter
>> text, but the whole field gets selected and pushed around the screen
>> instead.
> 
> 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 send them to them 
> after setting the 'style' property of your tool stacks to "modeless". (In the 
> latter case you can set the style back to "topLevel" to edit).
> 
> In either case, the stacks will load into the IDE permanently in browse mode.

That takes care of Tim's situation, but the general case of defaulting to the 
pointer tool is still an annoyance. If LC is not already running and I 
double-click on a stack to open it, then after the IDE loads and then my stack 
loads I get the pointer tool. Luckily I locloc all my buttons and fields or I'd 
be moving things around inadvertently until I remember I have to change to 
browse mode. I would love to be able to change this behavior in LC preferences.

-- Peter

Peter M. Brigham
pmb...@gmail.com
http://home.comcast.net/~pmbrig


___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode


Re: Default tool on open stack

2016-04-12 Thread Mark Waddingham

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
text, but the whole field gets selected and pushed around the screen
instead.


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 send 
them to them after setting the 'style' property of your tool stacks to 
"modeless". (In the latter case you can set the style back to "topLevel" 
to edit).


In either case, the stacks will load into the IDE permanently in browse 
mode.


Hope this helps!

Mark.

--
Mark Waddingham ~ m...@livecode.com ~ http://www.livecode.com/
LiveCode: Everyone can create apps

___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode


Re: Default tool on open stack

2016-04-12 Thread J. Landman Gay

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 
accidentally dragged some controls around on the projection screen 
before remembering to change to the browse tool. If anyone mentions that 
one of them was me, ignore it.


--
Jacqueline Landman Gay | jac...@hyperactivesw.com
HyperActive Software   | http://www.hyperactivesw.com

___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode


Re: Default tool on open stack

2016-04-11 Thread Mark Wieder

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
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode


Re: Default tool on open stack

2016-04-11 Thread Tim Selander

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 and pushed around the screen instead.


Tim Selander
Tokyo, Japan



On 16/04/12 8:23, Peter Bogdanoff wrote:

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 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 active.

Why???

Any help appreciated.

Tim Selander
Tokyo, Japan

___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode



___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode



___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: Default tool on open stack

2016-04-11 Thread Roger Guay
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 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, 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 Gay | jac...@hyperactivesw.com
>>> HyperActive Software   | http://www.hyperactivesw.com
>>> 
>>> 
>>> 
>>> On April 11, 2016 6:43:23 PM Roger Guay  wrote:
>>> 
 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
>   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 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 active.
>> 
>> Why???
>> 
>> Any help appreciated.
>> 
>> Tim Selander
>> Tokyo, Japan
>> 
>> ___
>> use-livecode mailing list
>> use-livecode@lists.runrev.com
>> Please visit this url to subscribe, unsubscribe and manage your 
>> subscription preferences:
>> http://lists.runrev.com/mailman/listinfo/use-livecode
> 
> 
> ___
> use-livecode mailing list
> use-livecode@lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your 
> subscription preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode
 
 ___
 use-livecode mailing list
 use-livecode@lists.runrev.com
 Please visit this url to subscribe, unsubscribe and manage your 
 subscription preferences:
 http://lists.runrev.com/mailman/listinfo/use-livecode
>>> 
>>> 
>>> 
>>> ___
>>> use-livecode mailing list
>>> use-livecode@lists.runrev.com
>>> Please visit this url to subscribe, unsubscribe and manage your 
>>> subscription preferences:
>>> http://lists.runrev.com/mailman/listinfo/use-livecode
>> 
>> ___
>> use-livecode mailing list
>> use-livecode@lists.runrev.com
>> Please visit this url to subscribe, unsubscribe and manage your subscription 
>> preferences:
>> http://lists.runrev.com/mailman/listinfo/use-livecode
> 
> 
> ___
> use-livecode mailing list
> use-livecode@lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your subscription 
> preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode

___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode


Re: Default tool on open stack

2016-04-11 Thread Peter Bogdanoff
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, 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 Gay | jac...@hyperactivesw.com
>> HyperActive Software   | http://www.hyperactivesw.com
>> 
>> 
>> 
>> On April 11, 2016 6:43:23 PM Roger Guay  wrote:
>> 
>>> 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
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 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 active.
> 
> Why???
> 
> Any help appreciated.
> 
> Tim Selander
> Tokyo, Japan
> 
> ___
> use-livecode mailing list
> use-livecode@lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your 
> subscription preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode
 
 
 ___
 use-livecode mailing list
 use-livecode@lists.runrev.com
 Please visit this url to subscribe, unsubscribe and manage your 
 subscription preferences:
 http://lists.runrev.com/mailman/listinfo/use-livecode
>>> 
>>> ___
>>> use-livecode mailing list
>>> use-livecode@lists.runrev.com
>>> Please visit this url to subscribe, unsubscribe and manage your 
>>> subscription preferences:
>>> http://lists.runrev.com/mailman/listinfo/use-livecode
>> 
>> 
>> 
>> ___
>> use-livecode mailing list
>> use-livecode@lists.runrev.com
>> Please visit this url to subscribe, unsubscribe and manage your subscription 
>> preferences:
>> http://lists.runrev.com/mailman/listinfo/use-livecode
> 
> ___
> use-livecode mailing list
> use-livecode@lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your subscription 
> preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode


___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode


Re: Default tool on open stack

2016-04-11 Thread Roger Guay
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 Gay | jac...@hyperactivesw.com
> HyperActive Software   | http://www.hyperactivesw.com
> 
> 
> 
> On April 11, 2016 6:43:23 PM Roger Guay  wrote:
> 
>> 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
>>> 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 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 active.
 
 Why???
 
 Any help appreciated.
 
 Tim Selander
 Tokyo, Japan
 
 ___
 use-livecode mailing list
 use-livecode@lists.runrev.com
 Please visit this url to subscribe, unsubscribe and manage your 
 subscription preferences:
 http://lists.runrev.com/mailman/listinfo/use-livecode
>>> 
>>> 
>>> ___
>>> use-livecode mailing list
>>> use-livecode@lists.runrev.com
>>> Please visit this url to subscribe, unsubscribe and manage your 
>>> subscription preferences:
>>> http://lists.runrev.com/mailman/listinfo/use-livecode
>> 
>> ___
>> use-livecode mailing list
>> use-livecode@lists.runrev.com
>> Please visit this url to subscribe, unsubscribe and manage your subscription 
>> preferences:
>> http://lists.runrev.com/mailman/listinfo/use-livecode
> 
> 
> 
> ___
> use-livecode mailing list
> use-livecode@lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your subscription 
> preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode

___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: Default tool on open stack

2016-04-11 Thread J. Landman Gay
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 6:43:23 PM Roger Guay  wrote:

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
 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 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 active.

Why???

Any help appreciated.

Tim Selander
Tokyo, Japan

___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your 
subscription preferences:

http://lists.runrev.com/mailman/listinfo/use-livecode



___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your 
subscription preferences:

http://lists.runrev.com/mailman/listinfo/use-livecode


___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your 
subscription preferences:

http://lists.runrev.com/mailman/listinfo/use-livecode




___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: Default tool on open stack

2016-04-11 Thread Roger Guay
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
>  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 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 active.
>> 
>> Why???
>> 
>> Any help appreciated.
>> 
>> Tim Selander
>> Tokyo, Japan
>> 
>> ___
>> use-livecode mailing list
>> use-livecode@lists.runrev.com
>> Please visit this url to subscribe, unsubscribe and manage your subscription 
>> preferences:
>> http://lists.runrev.com/mailman/listinfo/use-livecode
> 
> 
> ___
> use-livecode mailing list
> use-livecode@lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your subscription 
> preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode

___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode


Re: Default tool on open stack

2016-04-11 Thread Peter Bogdanoff
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 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 active.
> 
> Why???
> 
> Any help appreciated.
> 
> Tim Selander
> Tokyo, Japan
> 
> ___
> use-livecode mailing list
> use-livecode@lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your subscription 
> preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode


___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode


Default tool on open stack

2016-04-11 Thread Tim Selander
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 active.

Why???

Any help appreciated.

Tim Selander
Tokyo, Japan

___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode


AW: open stack finds stack in wrong path!?

2015-06-17 Thread Tiemo Hollmann TB
Devin, you were absolutely right,
I was using the wrong itemDel :(
Thank you for coaching
Tiemo

-Ursprüngliche Nachricht-
Von: use-livecode [mailto:use-livecode-boun...@lists.runrev.com] Im Auftrag
von Devin Asay
Gesendet: Montag, 15. Juni 2015 19:57
An: How to use LiveCode
Betreff: Re: 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.
 
 Because this software runs directly 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  mainStack.rev). The 
 splash stack opens correctly the mainStack in its bundle, only as far 
 there is no copy of the mainStack on bundle level. But as soon there 
 is a copy of the mainStack in the bundle directory (for windows use), 
 the OS X program ignores my given path within the bundle and opens the 
 mainStack from the bundle level, which I don't want to be used on OS X.
 
 Is there any secret hierarchy for looking for stackfiles and ignoring 
 given paths? Or am I overseeing something obviously?

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. But if you don’t try to
find a stackfile relative to the .app, it will look first in the folder that
contains the .app bundle. I think you can work around your problem by
including this in the preOpenStack or openStack handler of the splash
stack/app:

 if the environment is “development” then
   go stack item 1 to -2 of the effective filename of this stack  slash 
“mainStack.rev
 else
   go stack “mainStack.rev”
 end if

Why? Because once the stack is made into a standalone the defaultFolder
becomes the folder containing the .app bundle. It should therefore work in
both the Mac and Windows environments.

I hope I understood your problem correctly.

Devin


Devin Asay
Office of Digital Humanities
Brigham Young University


___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode


___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode


Re: open stack finds stack in wrong path!?

2015-06-17 Thread Devin Asay

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 think to put that into my sample code.

Glad you figured it out.

Devin

 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. But if you don't try to
 find a stackfile relative to the .app, it will look first in the folder that
 contains the .app bundle. I think you can work around your problem by
 including this in the preOpenStack or openStack handler of the splash
 stack/app:
 
 if the environment is development then
   go stack item 1 to -2 of the effective filename of this stack  slash 
 mainStack.rev
 else
   go stack mainStack.rev
 end if
 
 Why? Because once the stack is made into a standalone the defaultFolder
 becomes the folder containing the .app bundle. It should therefore work in
 both the Mac and Windows environments.
 
 I hope I understood your problem correctly.
 
 Devin
 
 
 Devin Asay
 Office of Digital Humanities
 Brigham Young University
 
 
 ___
 use-livecode mailing list
 use-livecode@lists.runrev.com
 Please visit this url to subscribe, unsubscribe and manage your subscription
 preferences:
 http://lists.runrev.com/mailman/listinfo/use-livecode
 
 
 ___
 use-livecode mailing list
 use-livecode@lists.runrev.com
 Please visit this url to subscribe, unsubscribe and manage your subscription 
 preferences:
 http://lists.runrev.com/mailman/listinfo/use-livecode

Devin Asay
Office of Digital Humanities
Brigham Young University


___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode


Re: open stack finds stack in wrong path!?

2015-06-16 Thread Devin Asay

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 do, my standalone always prefers the mainStack.rev from the
 bundle directory and ignores the given path inside the bundle. Only if there
 is no file mainStack.rev at the bundle level, the standalone takes the
 mainStack.rev from inside the bundle.
 Though there must be some more straight forward approach, the only solution
 I now see is using two different names of the mainStack.rev, one
 mainStackOSX.rev for OS X inside the bundle and one mainStackWin.rev at
 bundle level for the windows version, so that my OS X standalone can't catch
 the wrong stack at bundle level anymore. 
 Thanks

Could you create an alias (or dynamic link) from the bundle to the app 
directory? I don’t know if that would be any advantage, but at least you 
wouldn’t have to include two different copies of the mainstack. 

Beyond that, this seems like a bug to me (LiveCode recently changed the way 
they look for files in Mac .app bundles, and this may have been an unintended 
consequence.) It might be worth a bug report.

Devin


Devin Asay
Office of Digital Humanities
Brigham Young University


___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode


AW: open stack finds stack in wrong path!?

2015-06-16 Thread Tiemo Hollmann TB
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 do, my standalone always prefers the mainStack.rev from the
bundle directory and ignores the given path inside the bundle. Only if there
is no file mainStack.rev at the bundle level, the standalone takes the
mainStack.rev from inside the bundle.
Though there must be some more straight forward approach, the only solution
I now see is using two different names of the mainStack.rev, one
mainStackOSX.rev for OS X inside the bundle and one mainStackWin.rev at
bundle level for the windows version, so that my OS X standalone can't catch
the wrong stack at bundle level anymore. 
Thanks
Tiemo


-Ursprüngliche Nachricht-
Von: use-livecode [mailto:use-livecode-boun...@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 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
location of the splash stack/app, will look inside the .app bundle…



Devin Asay
Office of Digital Humanities
Brigham Young University


___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode


___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode


Re: open stack finds stack in wrong path!?

2015-06-15 Thread Devin Asay
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 location 
of the splash stack/app, will look inside the .app bundle…



Devin Asay
Office of Digital Humanities
Brigham Young University


___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode


Re: open stack finds stack in wrong path!?

2015-06-15 Thread Devin Asay

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.
 
 Because this software runs directly 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  mainStack.rev). The splash
 stack opens correctly the mainStack in its bundle, only as far there is no
 copy of the mainStack on bundle level. But as soon there is a copy of the
 mainStack in the bundle directory (for windows use), the OS X program
 ignores my given path within the bundle and opens the mainStack from the
 bundle level, which I don't want to be used on OS X.
 
 Is there any secret hierarchy for looking for stackfiles and ignoring given
 paths? Or am I overseeing something obviously?

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. But if you don’t try to 
find a stackfile relative to the .app, it will look first in the folder that 
contains the .app bundle. I think you can work around your problem by including 
this in the preOpenStack or openStack handler of the splash stack/app:

 if the environment is “development” then
   go stack item 1 to -2 of the effective filename of this stack  slash  
“mainStack.rev
 else
   go stack “mainStack.rev”
 end if

Why? Because once the stack is made into a standalone the defaultFolder becomes 
the folder containing the .app bundle. It should therefore work in both the Mac 
and Windows environments.

I hope I understood your problem correctly.

Devin


Devin Asay
Office of Digital Humanities
Brigham Young University


___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode


open stack finds stack in wrong path!?

2015-06-15 Thread Tiemo Hollmann TB
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.

Because this software runs directly 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  mainStack.rev). The splash
stack opens correctly the mainStack in its bundle, only as far there is no
copy of the mainStack on bundle level. But as soon there is a copy of the
mainStack in the bundle directory (for windows use), the OS X program
ignores my given path within the bundle and opens the mainStack from the
bundle level, which I don't want to be used on OS X.

Is there any secret hierarchy for looking for stackfiles and ignoring given
paths? Or am I overseeing something obviously?

Thanks for any hint

Tiemo

 

 

 

___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode


Re: Open stack problem

2014-07-15 Thread Bob Sneidar
More than likely, there is a script in the stack you open, or possibly the 
stack you are opening from, that has a runtime error that silently fails and 
script execution stops. But trying to explain why it works when you double 
click and not when you click the button would be much more difficult than, say, 
just waving a voodoo stick in the air and mumbling unspeakable things. 

Bob S


On Jun 8, 2014, at 10:39 , Peter Haworth p...@lcsql.com wrote:

 Trying to track down a strange problem involving opening a stack.
 
 I have a button with a script that issues an answer file statement to get
 the name of a stack file to open.  After getting the file name and doing a
 couple of checks I open the stack file then do some other stuff.
 
 This all works 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 a breakpoint on the open stack
 command, all works fine.
 
 I've removed all front scripts but same behavior.
 
 Any ideas?
 
 Pete
 lcSQL Software http://www.lcsql.com
 Home of lcStackBrowser http://www.lcsql.com/lcstackbrowser.html and
 SQLiteAdmin http://www.lcsql.com/sqliteadmin.html
 ___
 use-livecode mailing list
 use-livecode@lists.runrev.com
 Please visit this url to subscribe, unsubscribe and manage your subscription 
 preferences:
 http://lists.runrev.com/mailman/listinfo/use-livecode


___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode


Open stack problem

2014-06-08 Thread Peter Haworth
Trying to track down a strange problem involving opening a stack.

I have a button with a script that issues an answer file statement to get
the name of a stack file to open.  After getting the file name and doing a
couple of checks I open the stack file then do some other stuff.

This all works 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 a breakpoint on the open stack
command, all works fine.

I've removed all front scripts but same behavior.

Any ideas?

Pete
lcSQL Software http://www.lcsql.com
Home of lcStackBrowser http://www.lcsql.com/lcstackbrowser.html and
SQLiteAdmin http://www.lcsql.com/sqliteadmin.html
___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode


Android resize/open stack

2012-07-10 Thread Dan Friedman
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 device.  LiveCode on iOS doesn't 
seem to have this problem.  On iOS, the stack is resized BEFORE it is displayed.

Am I doing something wrong?  Is there some property I'm supposed to set? Is 
this a bug?  Is there a workaround for this?

Thanks in advance!
-Dan
___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode