Aha. Thanks. Richmond.
On 1/27/17 11:40 am, Tore Nilsen via use-livecode wrote:
The point of any pass-handler is to pass the message to the next level in the
message hierarchy. If you pass a message and the engine has a generic routine
to handle this message, you may end up with unexpected beh
The point of any pass-handler is to pass the message to the next level in the
message hierarchy. If you pass a message and the engine has a generic routine
to handle this message, you may end up with unexpected behavior in your
application. There is no need to pass any message unless you specifi
I wonder why a couple of people told me to remove 'pass copyKey' from:
on copyKey
answer "Export disabled in Demo"
pass copyKey
end copyKey
I did remove it and this seemed to make no difference at all . . .
So, the big question has to be; "What is the point of 'pass copyKey'?"
Richmond
_
Thank you, Klaus!
On 1/26/17 9:51 pm, Klaus major-k via use-livecode wrote:
Hi Richmond,
Am 26.01.2017 um 20:46 schrieb Richmond Mathewson via use-livecode
:
I'm trying to disable copying from textFields throughout a stack and tried this
in
the stackScript:
on copyKey
answer "Hard Cheese
Hi Richmond,
> Am 26.01.2017 um 20:51 schrieb Klaus major-k via use-livecode
> :
>
> Hi Richmond,
>
>> Am 26.01.2017 um 20:46 schrieb Richmond Mathewson via use-livecode
>> :
>>
>> I'm trying to disable copying from textFields throughout a stack and tried
>> this in
>> the stackScript:
>>
>
Hi Richmond,
> Am 26.01.2017 um 20:46 schrieb Richmond Mathewson via use-livecode
> :
>
> I'm trying to disable copying from textFields throughout a stack and tried
> this in
> the stackScript:
>
> on copyKey
> answer "Hard Cheese, Buster; this is a Demo!"
> pass copyKey
> end copyKey
>
> c
I think you don’t want to pass copyKey, but trap it.
> On Jan 26, 2017, at 2:46 PM, Richmond Mathewson via use-livecode
> wrote:
>
> I'm trying to disable copying from textFields throughout a stack and tried
> this in
> the stackScript:
>
> on copyKey
> answer "Hard Cheese, Buster; this is
