Wierdness and Bugs in Borland Products

Thread View: comp.windows.ms.programmer

3 messages

[T] Back to Threads [V] Tree View [G] Group Articles

3 total messages Started by Clayton Bridges Thu, 09 Apr 1992 20:31

#262

Author: Clayton Bridges
Date: Thu, 09 Apr 1992 20:31

22 lines
1604 bytes

I've got some strange problems with BC++ 3.0 and TPW. If anyone knows
a net address where I could send for help, please forward it to me.
Here are some of my problems. Post if you have solutions to these, or
similar problems.

* TDW -- I'm trying to track an Exc. 13 bug in some code which also
uses the 80x87. Whenever I try to trace into the code, I get a
"terminated, exit code 0", whenever I hit an fwait (with the 80x87
stack empty).  And when I don't trace into the code, I get the
Exception 13. Not fun.

* TCW, TPW -- The Borland-style dialog boxes are hosed in Win31. Is
there a bug fix to this or what? In addition, these guys really can't
handle the new font scheme very well.

* TCW -- the moving windows problem: I'll iconify a window in TCW, and
when I bring it back, it "disappears"; that is, it gets deiconified to
some random place on this huge TCW desktop (my only hint this was true
is that scroll bars get added to the desktop). Since I don't want to
spend 30 minutes in nowhere land looking for my window, I am forced to
cascade or tile the windows to get my "lost" window back to the "main"
part of the desktop.

Re: Wierdness and Bugs in Borland Products

#373

Author: Brent Langdon
Date: Tue, 14 Apr 1992 20:58

14 lines
1268 bytes

     In his posting, Clayton says that his borland-style buttons don't work.
I don't know where your problem lies.  I use Windows 3.1 and I have no
problem using the BWCC dialogs.

     In another note:  Has anybody noticed that in Borland Turbo 3.0 for
Windows, if the main window is not maximized and you have a text window
that is bigger than the main window but also not maximized, when you
use the cursor to scroll down the last text line on the screen is repeatedly
scrolled up.  Once you let the key up, the window is repainted as it should
be.  Not that big of a deal but sometimes little bugs such as that make one
wonder just exactly how reliable the entire product is.

                                   Brent Langdon
                                   Central Michigan University

Re: Wierdness and Bugs in Borland Products

#395

Author: Wolfgang Siebeck
Date: Wed, 15 Apr 1992 11:44

18 lines
1413 bytes

Brent Langdon <32JJCB3@CMUVM.CSV.CMICH.EDU> writes:

>     In another note:  Has anybody noticed that in Borland Turbo 3.0 for
>Windows, if the main window is not maximized and you have a text window
>that is bigger than the main window but also not maximized, when you
>use the cursor to scroll down the last text line on the screen is repeatedly
>scrolled up.  Once you let the key up, the window is repainted as it should
>be.  Not that big of a deal but sometimes little bugs such as that make one
>wonder just exactly how reliable the entire product is.

Well, I guess this is no bug. Since repainting takes so long, it is delayed
until no further scrolling is requested. The whole window is repainted when
the key is released. Can anyone confirm this? (sidney? hint, hint, ...)

Wolfgang
--
siebeck@infoac.rmi.de (Wolfgang Siebeck)
[ Yes, I got the T-shirt with my first release of Turbo-C :-) ]

Thread Navigation

This is a paginated view of messages in the thread with full content displayed inline.

Messages are displayed in chronological order, with the original post highlighted in green.

Use pagination controls to navigate through all messages in large threads.

Back to All Threads