Another is wanting to detect a mousedown event as opposed to a mouse click. In fact, if a mousedown could be detected, it should be possible to use that to enable drag/drop on a listbox ( as a mousedown method could trigger the enable methods) rather than the unusual click-lift-reclick and drag that exists now.

How about the event() returning meaningful return codes. Everything gets dumped back as a 1. but only mouse click, enter key anf function key are documented. Glen has informed me that internal to FRAME they trigger many events, eg when a mouse moves over a widget that has a changed cursor shape, when a frame is re-entered etc. Having some meaningful return codes would have helped Alex below. But I think the lastkey function may have helped him.

Don

Alex Wolf wrote: > > When a user presses an Enter Key and as the TextEntry that has the focus, now > executes. > so the user demanded that I enable the code under the field to also execute a > popup > list that is actually controlled by a command push button. This was ok - If you > pressed Enter > for the initial first selection. The Textentries associated SCL Linked to the > Popup List. The > intention was to use the command push button to repop the list as required. > > The problem was SAS does not have a way to disable the Enter Key so the user > found > it did something ! In the case when a user modified the text entry field and > clicked the > command push button, the result is the textfield changed so it's code is > executed first, > it links to the SCL code for the command push buttons SCL and then runs the Push > buttons SCL a second time. > > The point I am raising is that I have to resort to other means to ensure that > what > happens for first use and consequent uses does not do the above problem. In the > SQLWindows Product, the CLICK, DOUBLECLICK, ENTERKEY events are > trapped and the program can easily cover possible cases ! > > The problems in OOP programming in SAS are that a lot more development > effort is still needed to bring SAS to a level where it is a complete GUI > development > solution. > > Cheers > Alex Wolf > SAS Consultant ( and other things ) > in the land of OZ > > ---------- > From: Glen R. Walker[SMTP:sasgrw@unx.sas.com] > Sent: Saturday, June 29, 1996 6:55 AM > To: Alex Wolf > Subject: Re: SAS AF Executable also some Major SAS Gripes > > |> I have used/developed 6.10/6.11 Frame etc for 9 months and when a programmer > |> must dig through the mother of all manuals ( object Oriented Classes ), and > doAnother is wanting to detect a mousedown event as opposed to a mouse click. In fact, if a mousedown could be detected, it should be possible to use that to enable drag/drop on a listbox ( as a mousedown method could trigger the enable methods) rather than the unusual click-lift-reclick and drag that exists now.

How about the event() returning meaningful return codes. Everything gets dumped back as a 1. but only mouse click, enter key anf function key are documented. Glen has informed me that internal to FRAME they trigger many events, eg when a mouse moves over a widget that has a changed cursor shape, when a frame is re-entered etc. Having some meaningful return codes would have helped Alex below. But I think the lastkey function may have helped him.

Don

> |> extraordinary tricks and ruse's to make SAS Frame do what an advanced GUI > |> package does as standard, it is obvious SAS must spend a lot more > development > |> effort on the product !!! > > What's an example of a trick or a ruse that you had to do? > > Glen

-- ==========================+++++============================================ Don Stanley Don Stanley Consulting Services NEW ZEALAND DSTANLE@IBM.NET