Re: preOpenStack problem

[Sannyasin Brahmanathaswami via use-livecode]

confirmed.. happening here… I've been getting this since 8.1.5, never cause 
serious problem, and had no recipe, so could not report it.. but yes exactly 
this

debug breaking on preopenstack  

when closing up stacks.

BR

 

On 8/4/17, 11:06 PM, "use-livecode on behalf of Richmond Mathewson via 
use-livecode"  wrote:

why on earth is LiveCode trawling through "preOpenStack" when it's 
closing the thing?

___
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: preOpenStack

[Robert Brenstein]

On 07.09.2014 at 17:18 Uhr -0500 J. Landman Gay apparently wrote:


It seemed non-intuitive to me too that you could put a preOpenStack 
handler in a card, because the card wasn't open yet. That was 
wrong-thinking. I asked Mark Waddingham about it some years ago and 
he said that the entire stack has to load at once when it opens, 
otherwise there would be no way a script could manage any of the 
objects or card properties. The messages are sent in a specific 
order, but in reality the entire structure is already in RAM before 
the messaging starts.




It helps to mentally distinguish between loading the stack in memory, 
which happens before anything else as Jacqie says above, and 
rendering it on the screen, which is interwoven with certain messages.


RObert

___
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: preOpenStack

[Terence Heaford]

Thanks for your reply.

Putting it in the card script does seem to be the answer.

Had a quick look in the dictionary and I couldn’t find where it says do not put 
it in the stack script.
The dictionary just says the message is sent to the destination card when you 
open a stack.

It may be in some other docs somewhere.


All the best

Terry

 
On 06 Sep 2014, at 17:08, Mark Wieder mwie...@ahsoftware.net wrote:

 Terence-
 
 Saturday, September 6, 2014, 4:26:23 AM, you wrote:
 
 I have a stack(main stack) which in the stack script contains a
 preopenstack handler that I use to set the size of the window before
 it shows.
 
 The preopenstack and openstack class of handlers should be in the
 script of the first card, not in the stack script. Yes, it's in the
 docs. If these handlers are in the stack script you an easily run into
 the sort of problems you're encountering.
 
 -- 
 -Mark Wieder
 ahsoftw...@gmail.com
 
 This communication may be unlawfully collected and stored by the National 
 Security Agency (NSA) in secret. The parties to this email do not 
 consent to the retrieving or storing of this communication and any 
 related metadata, as well as printing, copying, re-transmitting, 
 disseminating, or otherwise using it. If you believe you have received 
 this communication in error, please delete it immediately.
 
 
 ___
 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: preOpenStack

[Terence Heaford]

Thanks for your reply.

Putting it in the card script does seem to be the answer.

Had a quick look in the dictionary and I couldn’t find where it says do not put 
it in the stack script.
The dictionary just says the message is sent to the destination card when you 
open a stack.

It may be in some other docs somewhere.


All the best

Terry

On 06 Sep 2014, at 17:08, Mark Wieder mwie...@ahsoftware.net wrote:

 Terence-
 
 Saturday, September 6, 2014, 4:26:23 AM, you wrote:
 
 I have a stack(main stack) which in the stack script contains a
 preopenstack handler that I use to set the size of the window before
 it shows.
 
 The preopenstack and openstack class of handlers should be in the
 script of the first card, not in the stack script. Yes, it's in the
 docs. If these handlers are in the stack script you an easily run into
 the sort of problems you're encountering.
 
 -- 
 -Mark Wieder
 ahsoftw...@gmail.com
 
 This communication may be unlawfully collected and stored by the National 
 Security Agency (NSA) in secret. The parties to this email do not 
 consent to the retrieving or storing of this communication and any 
 related metadata, as well as printing, copying, re-transmitting, 
 disseminating, or otherwise using it. If you believe you have received 
 this communication in error, please delete it immediately.
 
 
 ___
 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: preOpenStack

[Earthednet-wp]

Terence,
Interesting, but it seems counter-intuitive to have a handler that references 
the stack being required to be on a card script. Which card? I assume it's the 
card that first opens in the stack?
Bill

William Prothero
http://es.earthednet.org

 On Sep 7, 2014, at 12:02 AM, Terence Heaford t.heaf...@btinternet.com wrote:
 
 Thanks for your reply.
 
 Putting it in the card script does seem to be the answer.
 
 Had a quick look in the dictionary and I couldn’t find where it says do not 
 put it in the stack script.
 The dictionary just says the message is sent to the destination card when you 
 open a stack.
 
 It may be in some other docs somewhere.
 
 
 All the best
 
 Terry
 
 On 06 Sep 2014, at 17:08, Mark Wieder mwie...@ahsoftware.net wrote:
 
 Terence-
 
 Saturday, September 6, 2014, 4:26:23 AM, you wrote:
 
 I have a stack(main stack) which in the stack script contains a
 preopenstack handler that I use to set the size of the window before
 it shows.
 
 The preopenstack and openstack class of handlers should be in the
 script of the first card, not in the stack script. Yes, it's in the
 docs. If these handlers are in the stack script you an easily run into
 the sort of problems you're encountering.
 
 -- 
 -Mark Wieder
 ahsoftw...@gmail.com
 
 This communication may be unlawfully collected and stored by the National 
 Security Agency (NSA) in secret. The parties to this email do not 
 consent to the retrieving or storing of this communication and any 
 related metadata, as well as printing, copying, re-transmitting, 
 disseminating, or otherwise using it. If you believe you have received 
 this communication in error, please delete it immediately.
 
 
 ___
 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: preOpenStack

[Mark Wieder]

Terence Heaford t.heaford@... writes:

 Putting it in the card script does seem to be the answer.
 
 Had a quick look in the dictionary and I couldn’t find where it says do
not put it in the stack script.
 The dictionary just says the message is sent to the destination card when
you open a stack.

As you yourself quoted, the message is sent to the destination *card*.
The card has the first crack at handling the message.

If the handler is in the stack script then it's accessible at the root of
the message path from any stack in the ecosystem. Placing it in the card
script localizes its effect.

-- 
 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: preOpenStack

[Earthednet-wp]

Mark,
Ok, you answered my concern. I guess it's another item to add to the dictionary 
somehow.
Bill

William Prothero
http://es.earthednet.org

 On Sep 7, 2014, at 8:22 AM, Mark Wieder mwie...@ahsoftware.net wrote:
 
 Terence Heaford t.heaford@... writes:
 
 Putting it in the card script does seem to be the answer.
 
 Had a quick look in the dictionary and I couldn’t find where it says do
 not put it in the stack script.
 The dictionary just says the message is sent to the destination card when
 you open a stack.
 
 As you yourself quoted, the message is sent to the destination *card*.
 The card has the first crack at handling the message.
 
 If the handler is in the stack script then it's accessible at the root of
 the message path from any stack in the ecosystem. Placing it in the card
 script localizes its effect.
 
 -- 
 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

___
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: preOpenStack

[Mark Wieder]

Earthednet-wp prothero@... writes:

 
 Mark,
 Ok, you answered my concern. I guess it's another item to add to the
dictionary somehow.

Yeah, it's just one of those things that you learn along the way. It's only
intuitive in hindsight.

-- 
 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: preOpenStack

[dunbarx]

It actually is a bit counterintuitive that a card can receive a preOpenStack 
message. After all, the whole (ostensible) idea is that preOpenstack is sent 
before the stack opens, so how could there even be a card to send that message 
to.


It is all mainly a matter of drawing, though, not what is actually is 
existence. The wording is a bit misleading is all...


Craig



-Original Message-
From: Mark Wieder mwie...@ahsoftware.net
To: use-livecode use-livecode@lists.runrev.com
Sent: Sun, Sep 7, 2014 11:23 am
Subject: Re: preOpenStack


Terence Heaford t.heaford@... writes:

 Putting it in the card script does seem to be the answer.
 
 Had a quick look in the dictionary and I couldn’t find where it says do
not put it in the stack script.
 The dictionary just says the message is sent to the destination card when
you open a stack.

As you yourself quoted, the message is sent to the destination *card*.
The card has the first crack at handling the message.

If the handler is in the stack script then it's accessible at the root of
the message path from any stack in the ecosystem. Placing it in the card
script localizes its effect.

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

 
___
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: preOpenStack

[Dave Kilroy]

I guess it's part of flexibility of LiveCode where you can have things like
'mouseup' handlers in a group, field, card or stack - but for sure the
dictionary could be tweaked to make things clearer...



-
Some are born coders, some achieve coding, and some have coding thrust upon 
them. - William Shakespeare  Hugh Senior

--
View this message in context: 
http://runtime-revolution.278305.n4.nabble.com/preOpenStack-tp4682886p4682929.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: preOpenStack

[Peter M. Brigham]

You really have to understand the message path for this kind of thing to be 
clear. If you master the way messages get sent, passed, and handled, then it's 
actually obvious. If you don't know the message path, it seems 
counterintuitive. Knowing the message path backwards and forwards to the point 
where you don't even have to think about it much will go a long way towards 
fluid scripting. It takes a while.

-- Peter

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

On Sep 7, 2014, at 9:36 AM, Mark Wieder wrote:

 Earthednet-wp prothero@... writes:
 
 
 Mark,
 Ok, you answered my concern. I guess it's another item to add to the
 dictionary somehow.
 
 Yeah, it's just one of those things that you learn along the way. It's only
 intuitive in hindsight.
 
 -- 
 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


___
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: preOpenStack

[Bill Vlahos]

I encourage everyone who would like the notes to be updated to do so yourself 
by adding comments to the dictionary items.

This is a great feature of the documentation. Just scroll all the way down on a 
dictionary entry.

Bill Vlahos
_
InfoWallet (http://www.infowallet.com) is about keeping your important life 
information with you, accessible, and secure.
lcTaskList: (http://www.infowallet.com/lctasklist/index.htm)
RunRev lcTaskList Forum: (http://forums.runrev.com/viewforum.php?f=61)

On Sep 7, 2014, at 9:49 AM, Dave Kilroy d...@applicationinsight.com wrote:

 I guess it's part of flexibility of LiveCode where you can have things like
 'mouseup' handlers in a group, field, card or stack - but for sure the
 dictionary could be tweaked to make things clearer...
 
 
 
 -
 Some are born coders, some achieve coding, and some have coding thrust upon 
 them. - William Shakespeare  Hugh Senior
 
 --
 View this message in context: 
 http://runtime-revolution.278305.n4.nabble.com/preOpenStack-tp4682886p4682929.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

___
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: preOpenStack

[Richard Gaskin]

Terence Heaford wrote:

 Putting it in the card script does seem to be the answer.

 Had a quick look in the dictionary and I couldn’t find where it says
 do not put it in the stack script.
 The dictionary just says the message is sent to the destination card
 when you open a stack.

Whether we *should* or *shouldn't* do something depends on what we want 
to do.


Once we learn the basics of the message path (in the v6.6.2 User Guide 
this is in Section 5.3.2, p127), we can anticipate the flow of messages 
and use them as we need for the task at hand.


While it may be useful to put initialization things in the first card of 
the mainstack, having commonly-used routines in the mainstack script can 
be very useful.




William Prothero wrote:

 Interesting, but it seems counter-intuitive to have a handler that
 references the stack being required to be on a card script.

I believe this was introduced in HyperCard, and remains a foundational 
element in most xTalks.  It's useful in allowing us to overload or 
override how messages are handled differently if we choose based on the 
context of the current card.


 Which card? I assume it's the card that first opens in the stack?

This should always be the current card, so in a case where a stack is 
being opened the current card will be the first one.


That said, you can also open stacks via script with things like:

  open card 2 of stack SomeStack

...in which case the card script invoked will be for card 2, which gives 
us the flexibility of handling these sorts of messages however we might 
want for a given card.


--
 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: preOpenStack

[William Prothero]

Richard:
Tnx for the comments, all. 
Just to check my understanding of this issue:

So, the “on preopenstack” message, in a card script, will only get triggered 
once, when the stack is opened? It won’t get triggered when you go to another 
card with an “on preOpenStack” handler??

Bill

On Sep 7, 2014, at 1:02 PM, Richard Gaskin ambassa...@fourthworld.com wrote:

 Terence Heaford wrote:
 
  Putting it in the card script does seem to be the answer.
 
  Had a quick look in the dictionary and I couldn’t find where it says
  do not put it in the stack script.
  The dictionary just says the message is sent to the destination card
  when you open a stack.
 
 Whether we *should* or *shouldn't* do something depends on what we want to do.
 
 Once we learn the basics of the message path (in the v6.6.2 User Guide this 
 is in Section 5.3.2, p127), we can anticipate the flow of messages and use 
 them as we need for the task at hand.
 
 While it may be useful to put initialization things in the first card of the 
 mainstack, having commonly-used routines in the mainstack script can be very 
 useful.
 
 
 
 William Prothero wrote:
 
  Interesting, but it seems counter-intuitive to have a handler that
  references the stack being required to be on a card script.
 
 I believe this was introduced in HyperCard, and remains a foundational 
 element in most xTalks.  It's useful in allowing us to overload or override 
 how messages are handled differently if we choose based on the context of the 
 current card.
 
  Which card? I assume it's the card that first opens in the stack?
 
 This should always be the current card, so in a case where a stack is being 
 opened the current card will be the first one.
 
 That said, you can also open stacks via script with things like:
 
  open card 2 of stack SomeStack
 
 ...in which case the card script invoked will be for card 2, which gives us 
 the flexibility of handling these sorts of messages however we might want for 
 a given card.
 
 -- 
 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: preOpenStack

[William Prothero]

Richard, 
sorry for not being more clear.

I understand that if a stack is opened, then the preOpenStack handler is 
triggered (it is in the first card), but if I go to another card on the same 
stack with a different preOpenStack handler on it, I would assume the 
preOpenStack handler wouldn’t get triggered because a new stack hasn’t been 
opened. Easy to test, but I thought I’d ask.
Bill

On Sep 7, 2014, at 1:38 PM, Richard Gaskin ambassa...@fourthworld.com wrote:

 William Prothero wrote:
  Richard:
  Tnx for the comments, all.
  Just to check my understanding of this issue:
 
  So, the “on preopenstack” message, in a card script, will only get
  triggered once, when the stack is opened? It won’t get triggered when
  you go to another card with an “on preOpenStack” handler??
 
 Most non-control-specific system messages are sent to the card first (the 
 others being sent to the target control).  Like any other object, if you 
 handle it in that object's script and don't explicitly pass it, the message 
 won't travel any further.
 
 -- 
 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: preOpenStack

[J. Landman Gay]

On 9/7/2014, 3:55 PM, William Prothero wrote:

I understand that if a stack is opened, then the preOpenStack handler
is triggered (it is in the first card), but if I go to another card
on the same stack with a different preOpenStack handler on it, I
would assume the preOpenStack handler wouldn’t get triggered because
a new stack hasn’t been opened. Easy to test, but I thought I’d ask.


Right. The preOpenStack and openStack messages are only sent once when a 
stack first opens. It always opens on the first card. As a user you 
won't see that if a script requests card 2 of stack x but it still 
goes to card 1 first and then moves to card 2. I don't believe a 
preOpenStack handler on card 2 will ever trigger.


It seemed non-intuitive to me too that you could put a preOpenStack 
handler in a card, because the card wasn't open yet. That was 
wrong-thinking. I asked Mark Waddingham about it some years ago and he 
said that the entire stack has to load at once when it opens, otherwise 
there would be no way a script could manage any of the objects or card 
properties. The messages are sent in a specific order, but in reality 
the entire structure is already in RAM before the messaging starts.


--
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: preOpenStack

[jbv]

Hello,

When using preopenstack or openstack, I always check the name
of the stack, no matter which version of LC.

on openStack
   if short name of this stack contains my main stack then
  -- do something
   end if
end openStack

This way you're 100% safe.

Best
jbv


 I have a stack(main stack) which in the stack script contains a
 preopenstack handler that I use to set the size of the window before it
 shows.

 One of the datagrids on the card of this stack executes:

 on mouseDoubleUp theMouseButton
open stack “MyOtherStack as sheet
 end mouseDoubleUp

 Since I have started using 6.7 RC1 on my Mac when open stack
 “MyOtherStack as sheet is executed the sheet window is resized to that in
 the preopenstack handler of the main stack.

 on preOpenStack
set the width of this stack to 1080
set the height of this stack  to 700
 end preOpenStack

 Is this a bug?

 Does the preopenstack handler in the script of the main stack also get
 applied to the sheet window?

 It didn’t in earlier releases (DP’s).

 All the best

 Terry
 ___
 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: preOpenStack

[Terence Heaford]

Thanks for your response, I am aware of this solution but…

Is what I described correct or a bug?


Thanks

Terry


On 06 Sep 2014, at 12:32, j...@souslelogo.com wrote:

 Hello,
 
 When using preopenstack or openstack, I always check the name
 of the stack, no matter which version of LC.
 
 on openStack
   if short name of this stack contains my main stack then
  -- do something
   end if
 end openStack
 
 This way you're 100% safe.
 
 Best
 jbv
 
 
 I have a stack(main stack) which in the stack script contains a
 preopenstack handler that I use to set the size of the window before it
 shows.
 
 One of the datagrids on the card of this stack executes:
 
 on mouseDoubleUp theMouseButton
   open stack “MyOtherStack as sheet
 end mouseDoubleUp
 
 Since I have started using 6.7 RC1 on my Mac when open stack
 “MyOtherStack as sheet is executed the sheet window is resized to that in
 the preopenstack handler of the main stack.
 
 on preOpenStack
   set the width of this stack to 1080
   set the height of this stack  to 700
 end preOpenStack
 
 Is this a bug?
 
 Does the preopenstack handler in the script of the main stack also get
 applied to the sheet window?
 
 It didn’t in earlier releases (DP’s).
 
 All the best
 
 Terry
 ___
 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: preOpenStack

[Terence Heaford]

Thanks for your response, I am aware of this solution but…

Is what I described correct or a bug?


Thanks

Terry

On 06 Sep 2014, at 12:32, j...@souslelogo.com wrote:

 Hello,
 
 When using preopenstack or openstack, I always check the name
 of the stack, no matter which version of LC.
 
 on openStack
   if short name of this stack contains my main stack then
  -- do something
   end if
 end openStack
 
 This way you're 100% safe.
 
 Best
 jbv
 
 
 I have a stack(main stack) which in the stack script contains a
 preopenstack handler that I use to set the size of the window before it
 shows.
 
 One of the datagrids on the card of this stack executes:
 
 on mouseDoubleUp theMouseButton
   open stack “MyOtherStack as sheet
 end mouseDoubleUp
 
 Since I have started using 6.7 RC1 on my Mac when open stack
 “MyOtherStack as sheet is executed the sheet window is resized to that in
 the preopenstack handler of the main stack.
 
 on preOpenStack
   set the width of this stack to 1080
   set the height of this stack  to 700
 end preOpenStack
 
 Is this a bug?
 
 Does the preopenstack handler in the script of the main stack also get
 applied to the sheet window?
 
 It didn’t in earlier releases (DP’s).
 
 All the best
 
 Terry
 ___
 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: preOpenStack

[Peter M. Brigham]

If I understand correctly, what is happening is that the preopenstack message 
is getting passed through the MyOtherStack script and ends up going to the 
main stack script. One solution is to put an empty on preopenstack handler in 
the MyOtherStack script, to the message won't get to the mainstack script.

-- Peter

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

On Sep 6, 2014, at 9:12 AM, Terence Heaford wrote:

 Thanks for your response, I am aware of this solution but…
 
 Is what I described correct or a bug?
 
 
 Thanks
 
 Terry
 
 On 06 Sep 2014, at 12:32, j...@souslelogo.com wrote:
 
 Hello,
 
 When using preopenstack or openstack, I always check the name
 of the stack, no matter which version of LC.
 
 on openStack
  if short name of this stack contains my main stack then
 -- do something
  end if
 end openStack
 
 This way you're 100% safe.
 
 Best
 jbv
 
 
 I have a stack(main stack) which in the stack script contains a
 preopenstack handler that I use to set the size of the window before it
 shows.
 
 One of the datagrids on the card of this stack executes:
 
 on mouseDoubleUp theMouseButton
  open stack “MyOtherStack as sheet
 end mouseDoubleUp
 
 Since I have started using 6.7 RC1 on my Mac when open stack
 “MyOtherStack as sheet is executed the sheet window is resized to that in
 the preopenstack handler of the main stack.
 
 on preOpenStack
  set the width of this stack to 1080
  set the height of this stack  to 700
 end preOpenStack
 
 Is this a bug?
 
 Does the preopenstack handler in the script of the main stack also get
 applied to the sheet window?
 
 It didn’t in earlier releases (DP’s).
 
 All the best
 
 Terry
 ___
 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: preOpenStack

[jbv]

 Thanks for your response, I am aware of this solution but…

 Is what I described correct or a bug?



Honnestly I don't know. I had a similar problem as yours with
earlier versions of LC (4.5.3 IIRC), that's why I always use the
solution I mentioned. Therefore I don't if it also happens in
more recent versions.

jbv


___
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: preOpenStack

[J. Landman Gay]

One of the nice things about attending the conferences is that you overhear 
little asides the engineers drop into conversations.  Yesterday one of them 
said they'd rather we entered everything into the bug database, even if we 
aren't positive it's really a bug.  They'd rather know than miss something.  

I'm not sure if what you describe is a bug or a fix to something that used to 
be a bug, but I'd say let them know that the current behavior broke your 
scripts.  

On September 6, 2014 6:11:25 AM PDT, Terence Heaford t.heaf...@btinternet.com 
wrote:
Thanks for your response, I am aware of this solution but…

Is what I described correct or a bug?


Thanks

Terry


On 06 Sep 2014, at 12:32, j...@souslelogo.com wrote:

 Hello,
 
 When using preopenstack or openstack, I always check the name
 of the stack, no matter which version of LC.
 
 on openStack
   if short name of this stack contains my main stack then
  -- do something
   end if
 end openStack
 
 This way you're 100% safe.
 
 Best
 jbv
 
 
 I have a stack(main stack) which in the stack script contains a
 preopenstack handler that I use to set the size of the window before
it
 shows.
 
 One of the datagrids on the card of this stack executes:
 
 on mouseDoubleUp theMouseButton
   open stack “MyOtherStack as sheet
 end mouseDoubleUp
 
 Since I have started using 6.7 RC1 on my Mac when open stack
 “MyOtherStack as sheet is executed the sheet window is resized to
that in
 the preopenstack handler of the main stack.
 
 on preOpenStack
   set the width of this stack to 1080
   set the height of this stack  to 700
 end preOpenStack
 
 Is this a bug?
 
 Does the preopenstack handler in the script of the main stack also
get
 applied to the sheet window?
 
 It didn’t in earlier releases (DP’s).
 
 All the best
 
 Terry
 ___
 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

-- 
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: preOpenStack

[Mark Wieder]

Terence-

Saturday, September 6, 2014, 4:26:23 AM, you wrote:

 I have a stack(main stack) which in the stack script contains a
 preopenstack handler that I use to set the size of the window before
 it shows.

The preopenstack and openstack class of handlers should be in the
script of the first card, not in the stack script. Yes, it's in the
docs. If these handlers are in the stack script you an easily run into
the sort of problems you're encountering.

-- 
-Mark Wieder
 ahsoftw...@gmail.com

This communication may be unlawfully collected and stored by the National 
Security Agency (NSA) in secret. The parties to this email do not 
consent to the retrieving or storing of this communication and any 
related metadata, as well as printing, copying, re-transmitting, 
disseminating, or otherwise using it. If you believe you have received 
this communication in error, please delete it immediately.


___
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: preOpenStack on palette

[Richard Gaskin]

Mark Schonewille wrote:

 Why does the preOpenStack handler run when I use the palette command
 (even if the lockmessages are true) and what can I do against it?

Any system messages sent while messages are locked is a bug.  Please 
submit the recipe.


As for workarounds, you might consider a script-local flag that's set at 
the end of your preOpenStack handler, and read at the beginning so that 
if it's empty do nothing.


Shouldn't need that workaround though - please log the bug and post the 
RQCC# so I can cc myself on it.


Thanks -

--
 Richard Gaskin
 Fourth World
 LiveCode training and consulting: http://www.fourthworld.com
 Webzine for LiveCode developers: http://www.LiveCodeJournal.com
 LiveCode Journal blog: http://LiveCodejournal.com/blog.irv

___
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: preOpenStack on palette

[Mark Schonewille]

Richard,

Bug 9385.

I'm using that workaround but I don't like I.

--
Best regards,

Mark Schonewille

Economy-x-Talk Consulting and Software Engineering
Homepage: http://economy-x-talk.com
Twitter: http://twitter.com/xtalkprogrammer
KvK: 50277553

Download the Installer Maker Plugin 1.7 for LiveCode here http://qery.us/za

On 9 feb 2012, at 02:13, Richard Gaskin wrote:

 Mark Schonewille wrote:
 
  Why does the preOpenStack handler run when I use the palette command
  (even if the lockmessages are true) and what can I do against it?
 
 Any system messages sent while messages are locked is a bug.  Please submit 
 the recipe.
 
 As for workarounds, you might consider a script-local flag that's set at the 
 end of your preOpenStack handler, and read at the beginning so that if it's 
 empty do nothing.
 
 Shouldn't need that workaround though - please log the bug and post the RQCC# 
 so I can cc myself on it.
 
 Thanks -



___
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: preOpenStack and Breakpoints

[Bob Sneidar]

waves hand These aren't the droids you are looking for. Move along...

Bob


On Dec 7, 2010, at 11:34 PM, Mark Wieder wrote:

 There's a somewhat earlier version on revOnline with nag screens but
 otherwise fully functional.
 
 ...and...er...don't look at the PowerTools page. I haven't announced
 that one yet.
 
 -- 
 -Mark Wieder
 mwie...@ahsoftware.net


___
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: preOpenStack - Main stack script affects SubStack when it opens?

[Glen Bojsza]

Lots of options so I chose the to move my preOpenStack from the stack script
to script of card 1 and it works perfectly.

thanks,

On Tue, Dec 7, 2010 at 7:29 PM, Terry Judd t...@unimelb.edu.au wrote:

 This is normal behaviour. The ways around it are...

 1. an empty preopenstack handler in the substack
 2. stack specific code in the main stack preopenstack handler

 on preopenstack
   if the short name of me = [mainstack name] then
  do stuff
   end if
 end preopenstack

 3. move the preopenstack handler to the card script of the first card of
 the
 main stack

 Hopefully I've got that right.

 Terry...


 On 8/12/10 1:19 PM, Glen Bojsza gboj...@gmail.com wrote:

  Maybe it's me or should this not be happening. Livecode 4.5.1.
 
  I have a mainstack that has a preOpenStack that does some house
 keeping...
 
  I just added a substack that is opened from the mainstack by a user
 clicking
  a button.
 
  **There is NO preOpenStack in the substack
 
  When the substack opens the preOpenStack of the mainstack tries to run
 which
  generates an error since none of the objects on the mainstack are on the
  substack.
 
  Should preOpenStack only work with the stack that contains it?
 
  If this is the proper way the system works then what is the work around?
 
  thanks,
 
  Glen
  ___
  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

 --
 Dr Terry Judd | Senior Lecturer in Medical Education
 Medical Education Unit
 Melbourne Medical School
 The University of Melbourne



 ___
 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: preOpenStack - Main stack script affects SubStack when it opens?

[Scott Rossi]

If you move the preOpenStack handler to the script of the first card of the 
mainstack, the substack won't trigger the handler.  This is a common method of 
handling housekeeping and other routines that you want run at startup, but 
don't want triggered by substacks.

Regards,

Scott Rossi
Creative Director
Tactile Media, UX Design


On Dec 7, 2010, at 6:19 PM, Glen Bojsza gboj...@gmail.com wrote:

 Maybe it's me or should this not be happening. Livecode 4.5.1.
 
 I have a mainstack that has a preOpenStack that does some house keeping...
 
 I just added a substack that is opened from the mainstack by a user clicking
 a button.
 
 **There is NO preOpenStack in the substack
 
 When the substack opens the preOpenStack of the mainstack tries to run which
 generates an error since none of the objects on the mainstack are on the
 substack.
 
 Should preOpenStack only work with the stack that contains it?
 
 If this is the proper way the system works then what is the work around?
 
 thanks,
 
 Glen
 ___
 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: preOpenStack and Breakpoints

[Mike Kerner]

Well, never mind, I guess, I see I reported this bug as 7006 way back in the
v. 3 days and it is still listed as unconfirmed.  I also see that now, as
then, if I use breakpoint instead of a dot breakpoint, things work ok.
___
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: preOpenStack - Main stack script affects SubStack when it opens?

[Peter Haworth]

I think I've run into that and got round it by checking the name of  
this stack in the preOpenStack handler and only executing the rest  
of the script if I'm in the mainstack.  Actually, come to think about  
it, that was in a preOpenCard handler for a card in the main stack,  
not the main stack itself but I'm sure the same technique will work.


Pete Haworth

On Dec 7, 2010, at 6:19 PM, Glen Bojsza wrote:


Maybe it's me or should this not be happening. Livecode 4.5.1.

I have a mainstack that has a preOpenStack that does some house  
keeping...


I just added a substack that is opened from the mainstack by a user  
clicking

a button.

**There is NO preOpenStack in the substack

When the substack opens the preOpenStack of the mainstack tries to  
run which
generates an error since none of the objects on the mainstack are on  
the

substack.

Should preOpenStack only work with the stack that contains it?

If this is the proper way the system works then what is the work  
around?


thanks,

Glen
___
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: preOpenStack - Main stack script affects SubStack when it opens?

[Robert Brenstein]

On 07.12.2010 at 19:19 Uhr -0700 Glen Bojsza apparently wrote:

When the substack opens the preOpenStack of the mainstack tries to run which
generates an error since none of the objects on the mainstack are on the
substack.

Should preOpenStack only work with the stack that contains it?

If this is the proper way the system works then what is the work around?

thanks,

Glen



Move your preOpenStack from the stack script to script of card 1. 
What is happening is the result of message passing. In other words, 
it the proper way the system works. If your preOpenStack is on first 
card of the mainstack, it will execute only for the mainstack. An 
alternative could be to check in the preOpenStack if the active stack 
is the mainstack but it is simpler to move that handler.


Robert

___
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: preOpenStack and Breakpoints

[Peter Haworth]

I can only confirm that I've had the same problem many times, wish I  
had a solution for it.  Makes debugging pretty difficult.


Pete Haworth

On Dec 7, 2010, at 6:36 PM, Mike Kerner wrote:

Unrelated to the other preOpenStack problem reported in 4.5.1  
earlier by

someone else

I have a preOpenStack script with breakpoints in it.  But the  
breakpoints

never cause the script editor to come forward.  If I put an answer
preOpenStack line in the script the dialog will come up, but the
breakpoints still don't fire.

Is there some undocumented rhyme or reason for this?
___
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: preOpenStack and Breakpoints

[Mike Kerner]

I've reopened my bug report, so hopefully we can get it worked on.
___
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: preOpenStack and Breakpoints

[Mike Kerner]

Peter,
I also resubmitted it so the version would be updated.  It's bug 9219.  As a
workaround, instead of using a dot breakpoint, use the 'breakpoint' keyword.
___
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: preOpenStack - Main stack script affects SubStack when it opens?

[Terry Judd]

This is normal behaviour. The ways around it are...

1. an empty preopenstack handler in the substack
2. stack specific code in the main stack preopenstack handler

on preopenstack
   if the short name of me = [mainstack name] then
  do stuff
   end if
end preopenstack

3. move the preopenstack handler to the card script of the first card of the
main stack

Hopefully I've got that right.

Terry...


On 8/12/10 1:19 PM, Glen Bojsza gboj...@gmail.com wrote:

 Maybe it's me or should this not be happening. Livecode 4.5.1.
 
 I have a mainstack that has a preOpenStack that does some house keeping...
 
 I just added a substack that is opened from the mainstack by a user clicking
 a button.
 
 **There is NO preOpenStack in the substack
 
 When the substack opens the preOpenStack of the mainstack tries to run which
 generates an error since none of the objects on the mainstack are on the
 substack.
 
 Should preOpenStack only work with the stack that contains it?
 
 If this is the proper way the system works then what is the work around?
 
 thanks,
 
 Glen
 ___
 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

--
Dr Terry Judd | Senior Lecturer in Medical Education
Medical Education Unit
Melbourne Medical School
The University of Melbourne



___
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: preOpenStack and Breakpoints

[Mark Wieder]

Peter-

Tuesday, December 7, 2010, 6:45:35 PM, you wrote:

 I can only confirm that I've had the same problem many times, wish I
 had a solution for it.  Makes debugging pretty difficult.

cough
I should probably point out that PowerDebug handles this (and many
other former annoyances) properly.

...and I should also point out that the introductory price for
PowerDebug is going to expire at the end of the month.
/cough

http://www.ahsoftware.net/PowerTools/BuyPowerDebug.irev

-- 
-Mark Wieder
 mwie...@ahsoftware.net


___
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: preOpenStack and Breakpoints

[Mark Wieder]

Peter-

Tuesday, December 7, 2010, 11:08:46 PM, you wrote:

 That's a pretty nasty cough you have there Mark!  How can I download
 PowerDebug?  The link takes me to a place where I can buy it but the
 Downloads page just has Powertools (which also looks interesting).

There's a somewhat earlier version on revOnline with nag screens but
otherwise fully functional.

...and...er...don't look at the PowerTools page. I haven't announced
that one yet.

-- 
-Mark Wieder
 mwie...@ahsoftware.net


___
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