🚀 go-pugleaf

In article <92322.092615SASTPH@vm.sas.com>, SASTPH@vm.sas.com writes:
> Well, I thought I'd try converting a small Windows app written in C to
> Visual Basic 1.0, but it appears I can't.  Here's some things I that
> apparently can't be done in VB, or that I can't find in the doc:

> 2.  Send messages between forms.  My app uses three windows.   Clicking
>     on a control in the main window causes immediate changes to the
>     other two windows.

One way is to make a control, change the visible property to false, and use it's event procedures to transmit the message.

For example, a hidden textbox can be used.  Then the Text1_Change event sub
 can be used to interpet the message.  (The last thing it should to is
 empty itself.)

> 3.  Detect when the form is iconized. My app draws on its icon, which
>     I understand can be done in Visual Basic, but when?  In C I just
>     call IsIconic() whenever I get a WM_PAINT message and paint the
>     icon when it (IsIconic) returns TRUE.  While I'm aware that I
>     can call IsIconic from VB, surely I don't need to for such a
>     simple thing?

The property Form.WindowState gives this information.  (0 = Normal,
 1 = Minimized {iconic}, 2 = Maximized.)

Jon.

-- 
SAGER,JON EDWARD (ShadowBoxer)     |  Happy, Happy, Joy, Joy, Happy, Happy,
Internet: gt2438b@prism.gatech.edu |    Joy, Joy, Happy, Happy, Joy, Joy, Joy! 
Georgia Tech- The real University  | 
	      of Georgia           |           -Ren and Stimpy