🚀 go-pugleaf

Matt Arnold wrote:
> 
> craiga@netcom.com (Craig Arnush) writes:
> 
> >marnold@netcom.com (Matt Arnold) writes:
> >>
> >>Is this support only for OWL apps, or has Borland somehow gotten the
> >>16-bit COMMCTRL.DLL to work under Windows 3.1?  For example, using
> >>this Borland "emulation", could I write a "normal" Windows 3.1 app and
> >>get Windows 95 controls?
> 
> >That's exactly what the emulation gives you.  When writing a program for
> >Windows 3.1, you can have some of the Windows 95 controls via OWL's
> >emulation.
> 
> I meant "a normal Windows 3.1 app" to mean "a non-OWL 16-bit Windows
> app".
> 
> So your answer then is that this Windows 95-like control support is
> an "OWL thing" and I can't use it generically in any 16-bit program?
> OWL must be used to access the emulation.
>

Your whole program doesn't have to use OWL. You could write the parts 
that use the controls in OWL and leave the rest of it in regular C if 
you want. OWL doesn't interfere with regular old C type windows 
programming.

> 
> In any case, has Borland gotten the *actual* 16-bit COMMCTRL.DLL (the
> one that comes with Windows 95) to work under Windows 3.1, or is this
> emulation purely just that:  code, totally from Borland, that creates
> controls that look like Windows 95.
> 
> Regards,
> 

I went to the Borland presentation on BC++5.0 that was held here in 
Houston, Texas a few weeks ago and my understanding is that Borland 
wrote their own code to emulate(imitate) WIN95 controls in windows 3.x 
programs. It looked very good.



-- 
Hans
--------------------------------------------------------
hans@phoenix.phoenix.net 
--------------------------------------------------------