Re: Groups in the message path: Trapping Mouseup

2019-12-08 Thread Mark Wieder via use-livecode

On 12/8/19 4:04 PM, J. Landman Gay via use-livecode wrote:
I take that back, the card group shouldn't get the message. Sounds like 
something else is wrong.


A background group will definitely get the message before the stack 
script does. Also any script being used as a behavior.


--
 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: Groups in the message path: Trapping Mouseup

2019-12-08 Thread J. Landman Gay via use-livecode
I take that back, the card group shouldn't get the message. Sounds like 
something else is wrong.



On 12/8/19 5:24 PM, J. Landman Gay via use-livecode wrote:
Is the group that receives the mouseUp a card group or a background 
group? If I remember right, messages go from the button, to all card 
groups, then to the card, then all background groups, then to the stack.


So if it's a card group, it will get the message before the stack does.


On 12/8/19 1:55 PM, Sannyasin Brahmanathaswami via use-livecode wrote:

I think this a old problem that is re-surfacing. Or else it is known….

9.6 dp1, in the message path different independent groups are not 
encapsulated.


button "starWidget"
-- has no script
-- is not a part of any group

Stack script:

on mouseup
   put the short name of the target
   put the short name of the target into tTarget
   switch tTarget
    case(s) # various button names
    # consolidate all UI actions that not part of a group
    # to the stack script
   end switch
end mouseup

# the card are several groups,
# each with its own mouse handlers

# I click on button "starWidget"
-- nothing happens…hmm, no errors either…
# start profiling scripts (new trick I found)
# click on button "starWidget"
# stop profiling scripts:
   # Voila! the mouseup was trapped by one the other groups, 
as if they were in the message path.


Is there any way around this? Meanwhile I have to plug into every 
button explicit handlers. Tedious, make debugging painful…


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







--
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: Groups in the message path: Trapping Mouseup

2019-12-08 Thread J. Landman Gay via use-livecode
Is the group that receives the mouseUp a card group or a background 
group? If I remember right, messages go from the button, to all card 
groups, then to the card, then all background groups, then to the stack.


So if it's a card group, it will get the message before the stack does.


On 12/8/19 1:55 PM, Sannyasin Brahmanathaswami via use-livecode wrote:

I think this a old problem that is re-surfacing. Or else it is known….

9.6 dp1, in the message path different independent groups are not encapsulated.

button "starWidget"
-- has no script
-- is not a part of any group

Stack script:

on mouseup
   put the short name of the target
   put the short name of the target into tTarget
   switch tTarget
case(s) # various button names
# consolidate all UI actions that not part of a group
# to the stack script
   end switch
end mouseup

# the card are several groups,
# each with its own mouse handlers

# I click on button "starWidget"
-- nothing happens…hmm, no errors either…
# start profiling scripts (new trick I found)
# click on button "starWidget"
# stop profiling scripts:
   # Voila! the mouseup was trapped by one the other groups, as if they 
were in the message path.

Is there any way around this? Meanwhile I have to plug into every button 
explicit handlers. Tedious, make debugging painful…

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




--
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: Groups in the message path: Trapping Mouseup

2019-12-08 Thread dunbarx--- via use-livecode
Hi.
It is hard for me to understand without more info about the case statements. 
But when you have this:
# I click on button "starWidget"
-- nothing happens…hmm, no errors either…
Do you really mean nothing, not even that the:
   put the short name of the target

does not fire?
Craig

-Original Message-
From: Sannyasin Brahmanathaswami via use-livecode 

To: How LiveCode 
Cc: Sannyasin Brahmanathaswami 
Sent: Sun, Dec 8, 2019 2:56 pm
Subject: Groups in the message path: Trapping Mouseup 

I think this a old problem that is re-surfacing. Or else it is known….

9.6 dp1, in the message path different independent groups are not encapsulated.

button "starWidget"
-- has no script
-- is not a part of any group

Stack script:

on mouseup
          put the short name of the target
          put the short name of the target into tTarget
          switch tTarget
                  case(s) # various button names
                  # consolidate all UI actions that not part of a group
                  # to the stack script
          end switch
end mouseup

# the card are several groups,
# each with its own mouse handlers

# I click on button "starWidget"
-- nothing happens…hmm, no errors either…
# start profiling scripts (new trick I found)
# click on button "starWidget"
# stop profiling scripts:
          # Voila! the mouseup was trapped by one the other groups, as if they 
were in the message path.

Is there any way around this? Meanwhile I have to plug into every button 
explicit handlers. Tedious, make debugging painful…

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


Groups in the message path: Trapping Mouseup

2019-12-08 Thread Sannyasin Brahmanathaswami via use-livecode
I think this a old problem that is re-surfacing. Or else it is known….

9.6 dp1, in the message path different independent groups are not encapsulated.

button "starWidget"
-- has no script
-- is not a part of any group

Stack script:

on mouseup
  put the short name of the target
  put the short name of the target into tTarget
  switch tTarget
   case(s) # various button names
   # consolidate all UI actions that not part of a group
   # to the stack script
  end switch
end mouseup

# the card are several groups,
# each with its own mouse handlers

# I click on button "starWidget"
-- nothing happens…hmm, no errors either…
# start profiling scripts (new trick I found)
# click on button "starWidget"
# stop profiling scripts:
  # Voila! the mouseup was trapped by one the other groups, as if they 
were in the message path.

Is there any way around this? Meanwhile I have to plug into every button 
explicit handlers. Tedious, make debugging painful…

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: How to revoke that bottom pane of the script editor?

2019-12-08 Thread Klaus major-k via use-livecode
Hi Craig,

> Am 08.12.2019 um 15:45 schrieb dunbarx--- via use-livecode 
> :
> 
> Klaus.
> Type CMD-F as if you were trying to simply find something. All those lower 
> tools will reappear.

thanks, already tried that, no cigar...

> Craig

Best

Klaus

--
Klaus Major
https://www.major-k.de
kl...@major-k.de


___
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: How to revoke that bottom pane of the script editor?

2019-12-08 Thread dunbarx--- via use-livecode
Klaus.
Type CMD-F as if you were trying to simply find something. All those lower 
tools will reappear.
Craig


-Original Message-
From: Bob Sneidar via use-livecode 
To: How to use LiveCode 
Cc: Bob Sneidar 
Sent: Fri, Dec 6, 2019 5:02 pm
Subject: Re: How to revoke that bottom pane of the script editor?

Do you see the two horizontal lines at the bottom of the window? That is the 
handle for those panes. Try dragging it up. If you do not see those, not sure 
what has happened. 

Bob S


> On Dec 6, 2019, at 13:21 , Klaus major-k via use-livecode 
>  wrote:
> 
> Hi all,
> 
> in the script editor we ususally have three panes:
> 1. List of handlers on the left
> 2. The actual script on the right
> 3. At the botton we see the content of variables when debugging etc.
> 
> Now I somehow managed to make the bottom pane disappear 8-), 
> how can I get it back without to quit LC and trash the LC prefs?
> 
> Thanks for any hint!
> 
> 
> Best
> 
> Klaus
> --
> Klaus Major
> https://www.major-k.de
> kl...@major-k.de


___
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