gyugyi@portia.Stanford.EDU (Paul Gyugyi) (03/22/90)
I ran across a nasty problem in Actor. I create a window on the screen, and then create a button using B1 := newPush(Button, ...) with the previously created window as the parent. I set cRect and do a moveWindow and a show(B1, 1) [all of which ends up putting the button on the lient area of the window. Note that this is not in a dialog box, but just a free standing button]. So I click on the button, and it blinks, and I get a message at the parent window just like I should. Also, the text in the button is surrounded by a dotted line, showing that the button has the input focus. I can click to my heart's content and it works just like it should. However, if I hit a key while the button has the input focus, several thousands of dollars of hardware goes off into la-la land. The mouse still moves, but has no effect. I'm afraid I didn't check to see if bakground tasks still run. Alt-esc doesn't change windows, etc. Does normal C code have this problem? Actor looks like it's just passing most stuff through to windows. I'm running Actor 2.0 and MS Windows 2.11, MS Dos 4.01, Video7 1024i card (I chose it over the ATI card because Video 7 had more drivers and supported win/386, suggesting they're more likely to update to a win3 driver. ATI looked like they weren't serious about windows drivers) Any ideas? -Paul Gyugyi gyugyi@portia