Path: utzoo!utgpu!news-server.csri.toronto.edu!clyde.concordia.ca!uunet!tut.cis.ohio-state.edu!zaphod.mps.ohio-state.edu!rpi!jonathan From: jonathan@itsgw.rpi.edu (Jonathan Fisher) Newsgroups: comp.sys.mac.programmer Subject: Re: Wishlist for THINK _C_ (4.1 ? 5.0 ?) Message-ID: Date: 30 Mar 90 01:59:35 GMT References: <3192@draken.nada.kth.se> <2274@cbnewsk.ATT.COM> <3200@draken.nada.kth.se> <90083.132800CXT105@psuvm.psu.edu> <2993@murtoa.cs.mu.oz.au> <16903@well.sf.ca.us> Organization: Rensselaer Polytechnic Institute, Troy NY Lines: 20 In article <16903@well.sf.ca.us> nilesinc@well.UUCP (Avi Rappoport) writes: >What I really need is a way to keep my breakpoints and variables between >runs of the program. So annoying to have to keep resetting them. > Yes. That and a moveable or resizeable console window!! I use Think C for my Systems Programming Class, and we have to use a unix system. So I use Think C with the console window and the special command line (gasp) arguments function. But when using the debugger, I can't move the console window out of the way so that I could see the debugger windows. Every time that the program starts to run the console window comes to the front and hides the debugger windows. I am using a SE and no other screen. This renders auto-trace totally useless. If there is a way around this, someone please let me know! -- Jonathan Fisher jonathan@pawl.rpi.edu ITS Student Consultant or Rensselaer Polytechnic Institute userganu@rpitsmts.bitnet GO VIKINGS! Central Division Champs => NFC Champs => Superbowl XXV Champs