🚀 go-pugleaf

> In article <1991Jun19.215304.13141@cbnewsj.att.com> lk@cbnewsj.att.com (lisa.a.krauth) writes:
> >With version 2.1 of the SDK you did not need to press ctrl-enter to
> >move to the next line.  The enter key would move you to the next line
> >in the editbox.  Is this (ctrl-enter) something new in 3.0?  I have
> >also been struggling with the MLE trying to get it to behave as it did
> >with version 2.1 of the SDK.  Can anyone shed some more light on this
> >subject?  Why has the behavior changed?
> >
> >In article <1991Jun19.185843.2195@hyper.hyper.com>, bonneau@hyper.hyper.com (Paul Bonneau) writes:
> Sorry for the misunderstanding.  Even in win 3.0, a plain
> simple <enter> will insert a new-line into the MLE.  The
> problem is that the dialog manager will never let it happen.
> As for <ctrl>-<enter>, it is not an implementation
> restriction but rather what Microsoft's own windows apps do
> (for example Edit Summary Info in W4W).
> 
> You can use just plain old <enter> if you want, if you are
> willing to go through the hoops I described.  Also, I don't
> think the behaviour *has* changed.  I seem to recall that
> hitting <enter> in a win 2.x dialog would always activate
> the Default PushButton, regardless of the keyboard focus.
> 
> cheers - Paul Bonneau.

Maybe I still do not understand what you are saying, but this is
my experience:
I wrote an application using the 2.1 SDK.  The application has a dialog
box that has a multiline autoscroll editbox and a 2 pushbuttons (OK, CANCEL).
In the 2.1 application if I gave focus to the editbox, typed in a line of
text and hit return, I would move to the next line in the editbox.  When
I ported the code to version 3.1 of the SDK, the editbox no longer worked
this way.  Now when I enter a line of text in the editbox and hit enter,
it looks like the OK button gets depressed, but the code to be executed
when the OK is depressed does not execute.  I must explicitly use the mouse
to press the OK button to make the dialog box go away.  So it seems to
me that something has changed, and it almost seems like a bug.  I sure
hate losing functionality with a new release of software.  I'm going to
be even more unhappy if I have to write new code to give me what I got
for free before.  Please, someone tell me this isn't true!

Lisa Krauth
att!lzatt!lak