Xref: utzoo comp.lang.pascal:6110 comp.windows.ms.programmer:1798 Newsgroups: comp.lang.pascal,comp.windows.ms.programmer Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!wuarchive!csus.edu!borland.com!sidney From: sidney@borland.com (Sidney Markowitz) Subject: Re: TPWin: A really spiffy windows aplication but far from perfect Message-ID: <1991Apr12.010207.18663@borland.com> Organization: Borland International References: <1991Apr11.234826.8912@agate.berkeley.edu> Date: Fri, 12 Apr 1991 01:02:07 GMT magid@sandstorm.Berkeley.EDU (Paul Magid) writes: >If you have a graphics card with a resolution greater than 640x480 forget about >using the debugger. After you exit your screen is messed up and windows is >unusable. This forces you to exit and restart windows. This is totally >unacceptable. I called Borland and the tech support person there blamed it on >the dll that Borland got from Microsoft to do debugging. (When in trouble pass >the buck) I then asked whether there was a fix in the works, because this IS A >BUG, and she said that she could not tell me because they are relying on >Microsoft. This is not true. It's one of the few things about Windows that we *can't* blame on a Microsoft DLL :-). I'm sorry about that you received misinformation. Check out the code I posted the other day to comp.windows.ms.programmer, which can be run to clean the screen after you exit TDW. It works best if you use a shell program that lets you attach it to a hot key, because then you don't need to be able to see anything on the messed up screen in order to run it. A slightly more awkward alternative is to run a dummy bat file, which causes Windows to blank and repaint the screen when it goes to and from full screen mode. >If you use TPW and you have a graphics card with resolution greater than 640x480 >mail "bugs@borland.com" because this is a bug and it needs to be fixed, and >maybe if they get enough e-mail they will not respond in a slothful manner. There is no need. This is already being addressed as a high priority item. It is tricky, because we lose some of the Windows device independence features by tricking it into acting as a text-mode debugger, but we are working on it. >On another subject I tried to get the icons out of Winword but the resource toolkit informed me that it was not a win 3 app. What absolute rubbish! Is there >a way around this, and what exactly is going on here? {I do have version 1.1a} That's because Winword is a Windows 2 app that has been just been marked as a Window 3 app. There's not much interesting there anyway, just a bunch of cursors and the one icon :-). There used to be a product on the market, Resource Workshop, from EdenSoft, that could handle both Windows 2 and 3 files, but I don't know of anything currently available that does that. -- sidney markowitz