CommandKeyDown in a library script?

Graham Samuel livfoss at mac.com
Fri Jul 18 05:00:16 EDT 2014


Craig - sorry, forgot to thank you for this. Yes, there was another handler further up the library which I didn't notice. The IDE did not complain that I had two identically-named handlers in the same script, which seems odd to me. I wonder if it's a bug? I think the IDE used to complain about this, didn't it? It certainly doesn't now (just to be sure, I just added an "openStack" handler to a stack script which already has one, and it compiled without errors). I'm using LC 6.6.2.

Thanks again

Graham
On 16 Jul 2014, at 05:51, dunbarx at aol.com wrote:

> Graham.
> 
> 
> It should. It always has for me.
> 
> 
> Is the handler in the library stack in the stack script? It has to be, unless you send it explicity to a card or control on that stack. Are you sure you are not trapping it anywhere in the main stack? Or if you are, are you sure you are passing the message?
> 
> 
> Craig
> 
> 
> 
> -----Original Message-----
> From: Graham Samuel <livfoss at mac.com>
> To: How to use LiveCode <use-livecode at lists.runrev.com>
> Sent: Tue, Jul 15, 2014 1:51 pm
> Subject: CommandKeyDown in a library script?
> 
> 
> When I create a new mainstack and put a commandKeyDown handler in it, the 
> handler fires when I press the relevant key. When I put the same code in a 
> library stack, which is used via a "start using" command at initialisation, it 
> doesn't seem to fire. Can anyone say why?
> 
> TIA
> 
> Graham
> 
> _______________________________________________
> use-livecode mailing list
> use-livecode at 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 at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode





More information about the use-livecode mailing list