Xref: utzoo comp.sys.ibm.pc.misc:8333 comp.windows.ms.programmer:1722 Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!sol.ctr.columbia.edu!emory!hubcap!ncrcae!ncr-sd!iss-rb!booboo!davel From: davel@booboo.SanDiego.NCR.COM (David Lord) Newsgroups: comp.sys.ibm.pc.misc,comp.windows.ms.programmer Subject: Using Borland C++ Message-ID: <1991Apr5.171426.28904@SanDiego.NCR.COM> Date: 5 Apr 91 17:14:26 GMT Sender: @SanDiego.NCR.COM Reply-To: davel@booboo.SanDiego.NCR.COM (David Lord) Organization: NCR Corporation, Rancho Bernardo Lines: 51 Is there someplace on the net where people are discussing Borland C++? We don't seem to receive comp.windows.ms.programmer here, something I hope to have corrected. I am crossposting this there anyway since it seems like the appropriate place. Overall I like the compiler and the IDE alot except that I don't really want to learn a new text editor so I use Windows to go back and forth between BC++ and Elvis. I do have a number of complaints which I intend to call Borland about but I'm wondering if other people are having the same problems (or not having them). 1) Linking even a minimal Windows program on my 386SX takes twenty minutes. Using Hyperdisk in Staged Write mode will cut the time down to about five. 2) Using the debugger TDW causes my mouse cursor to vanish in Windows. The result is that I have to exit Windows everytime I finish with the debugger. Anyone know a way around this? I'm running Windows in 386 enhanced mode, my mouse is a three button Qtronix Mighty Cat, unusual perhaps but I've never had a problem with any other program. I load the mouse driver as MOUSE.SYS in my CONFIG.SYS. I have now found a rather kludgy way around it, I wrote a windows program which calls ShowCursor(1). After exiting the debugger I run this program and it gives me my cursor back. 3) The Menu Editor (Whitewater Resources Toolkit) is all but unusable. If I add or delete a menu item, any existing items with the 'grayed' attribute still say 'grayed' but don't get treated as grayed. I have to remove the 'grayed' attribute from each one and then put it back. Also I have had the system crash in this program just from clicking on the scroll after deleting menu items. The rest of the WRT seems to work adequately although the Dialog Box Editor doesn't always behave the way I think it should. Oh, one other bit of information for anyone thinking of buying BC++ to write Windows applications, expect to pay another $40 for Microsoft's Windows Programmer Reference. Also, if you're upgrading from TC++ expect to shell out for Peltzold's (sp?) book on Windows programming (I hear that you get this free if you are buying BC++ outright rather than as an upgrade.) I've also read that Borland is sending the Windows Help compiler to registered owners of BC++. If so they don't seem to be in a big hurry about it. If I seem to be making a lot of complaints, I should say that I'd still take this product over Microsoft "C" any day. -- Dave.Lord@SanDiego.NCR.COM Opinions expressed are my own and usually contrary to those of my employer.