Newsgroups: comp.windows.ms.programmer Path: utzoo!utgpu!watserv1!daemon From: tom@mims-iris.waterloo.edu (Tom Haapanen) Subject: Re: Borland C++ 2.0 impressions Message-ID: <1991Apr3.040856.29446@watserv1.waterloo.edu> Sender: daemon@watserv1.waterloo.edu Organization: University of Waterloo, WATMIMS Research Group References: <1991Apr1.122952.17519@watserv1.waterloo.edu> <1991Apr2.023939.13615@appmag.com> Date: Wed, 3 Apr 1991 04:08:56 GMT Lines: 22 tom@mims-iris.waterloo.edu (Tom Haapanen) writes: % And as to the Whitewater Resource toolkit: % - include files can't be used Todd Day writes: > Yes, they can. They just can't have anything in them except > #define's. No problem. I just have two files called "resource.rec" > and "resource.h" that contain all of the necessary resources for > my program (no use in splitting them up since WRT can deal with > all sorts of different resources being in one file). My mistake. However, WRT's dialog editor still doesn't have a status box or bar, and doesn't give any decent feedback when moving controls. Yuk. ***NOTE*** All my griping about the faults of BCC and WRT doesn't mean that BCC is a bad package. It means that it's not perfect, and if you're doing profes- sional Windows development, I wouldn't throw out the MSC and SDK just yet. Nevertheless, I expect to be using BCC in the months to come... [ \tom haapanen --- university of waterloo --- tom@mims-iris.waterloo.edu ] [ "i don't even know what street canada is on" -- al capone ]