Cmd-A doesn't work from Keyboard in Standalone

Sivakatirswami katir at
Fri Nov 18 00:50:58 EST 2005

Sarah: I send it up to support and Jacqueline writes... wonder of  
wonders -- something I haven't known for  years:


Aloha, Jacqueline:

Outstanding! thank you... solutions... "Without either a real menu bar "

FYI, this I don't think is explicitely documented (thus my  
consternation over failing cmd keys for several years now...)

All it says is:

"* Putting the / character anywhere in a line makes the next  
character the keyboard equivalent for the menu item. Neither the /  
nor the character following it appear in the menu, nor do they appear  
in the parameter to the menuPick message.

And the tool tips for the Rev Tools all say "Popup menu" "pulldown  
menu" all imply a menu, and other feature of menus as described in  
"Menus and the Menu Bar" topics section *do* work just fine whether  
the button in a group that  is hoisted to menu status or not (e.g.  
cascading behavior) You might consider adding this that topic section  
*and* to each of the  keyword definitions for  Popup, pulldown and  
option buttons.

Thanks you I can now fix this :-)!


On Nov 17, 2005, at 6:21 AM, Runtime Revolution Support wrote:
> Dear Sivakatirswami,
> The problem would be that you haven't designated the buttons as an  
> actual
> menu, so the engine is ignoring the keyboard shortcuts. Those will  
> only work
> if you set up a real menubar and assign it as the stack's menu. If  
> you do not
> want your menubar to go into the Mac's main menu area, then you can  
> set the
> editmenus to true on openstack so that the stack does not scroll
> Alternately, if you want to keep your layout the way it is now  
> without a real
> menu bar, write a commandKeyDown handler to manage command-key  
> presses.
> Without either a real menu bar or a commandkey handler, Rev has no  
> way of
> knowing what to do with those keyboard shortcuts so it ignores them.
> Jacqueline

On Nov 16, 2005, at 7:38 PM, Sarah Reichelt wrote:

> On 11/17/05, Sivakatirswami <katir at> wrote:
>> I wish... (I found a blocking handler) but no... there is nothing in
>> the stack to block the key down msg. I'm also getting this in a
>> nother button with "Save/S"
>> Case "Save"
>>    save this stack
>>     break
>> which appears fine in the menu, works fine from the menu, but doing
>> cmd-S from the keyboard does nothing... which, is scary because users
>> are thinking the app is being saved, but it's not...
>> I could send the stack for testing if that would help, would that be
>> OK? (who would like to test it for me?)
> I'll give it a go, if you like to send it along.
> Sarah
> _______________________________________________
> use-revolution mailing list
> use-revolution at
> Please visit this url to subscribe, unsubscribe and manage your  
> subscription preferences:

More information about the Use-livecode mailing list