I think there are still a few things in the edges and corners of Livecode that have been ignored and worked around, and bug reports not filed.
A good example of an popup menu that is on the plugin Settings panel in the Development menu. The popup list, in addition to being the stack file names as opposed to stack names, is also not alphabetized. This has been this way since at least version 2.x of Rev A little thing, probably not worth fixing, but an IDE anomaly that irks me every time I have to do something with plugins. But I don't spend a lot of time configuring plugins. Give a choice between fixing these little things, I'd rather have them continue their building the a new full featured text field or built-in SFTP support. Regarding the default button issue - quite frankly I'd rather have Livecode give me the primitives and give me the ability to work with the messages. So adding a simple script to activate it isn't that big a deal. If the button automatically sent out messages on return, it might require a script somewhere to defeat that automatic behavior. Probably a design decision that didn't get reflected in the docs. sqb On 1 September 2011 09:06, <dunb...@aol.com> wrote: > Jacque. > > > Me, too. > > > The dictionary talks a great game, though. It is the unrepeatable > intermittent aspect that has me stumped. I DID get an answer to my "answer > the defaultButton of this cd" a couple of times, but cannot any longer. As > for the dictionary's comments about the defaultButton "changing its size", > etc. I never saw any of that. > > > This was all tried in a new mainStack with two rectangle buttons and a > single default button. > > > Craig > > > -----Original Message----- > From: J. Landman Gay <jac...@hyperactivesw.com> > To: How to use LiveCode <use-livecode@lists.runrev.com> > Sent: Thu, Sep 1, 2011 7:22 am > Subject: Re: Default Button > > > On 8/31/11 7:29 PM, Pete wrote: > > I put a default button a card that has a couple of field controls on it. > > The field controls all have lockText set to true and traversalOn set to > > false. Pressing the return key when the card is active does not execute > the > > mouseUp handler for the default button as claimed by the dictionary. Is > > there some other setting of the card/button/controls that I have to use? > > Funny, I never knew about this capability. I've always had to script it > with a returnKey handler in the card, I've never seen a default behavior. > > -- > 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 > > > _______________________________________________ > 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 > -- Stephen Barncard San Francisco Ca. USA more about sqb <http://www.google.com/profiles/sbarncar> _______________________________________________ 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
