Subj : video issues w/ applications compiled w/ Borland CPP
To   : borland.public.cpp.borlandcpp
From : tgm
Date : Tue Sep 28 2004 10:01 am

I'm not familiar with this newsgroup, so please bear with me.

I have run into some issues with applications that have been compiled with
the Borland CPP compiler.  This involves separate applications from totally
different developers, so it appears that the compiler is the issue.  Here
are the video related bugs that I am seeing:

1.  Windows desktop icons are split.  The icons are in the desktop space
directly under the main application titlebar do NOT refreshed properly when
the application is minimized.  The portion of the icon under the titlebar is
blank and shows the desktop background only.  The rest of the icon (not
under the titlebar) does display properly; this includes portions previous
below the application main area.

2.  The Windows screen saver does NOT operate if a Borland compiled
application is displayed on the screen.  If the application is minimized,
the screen saver operates normally.  It does not matter if the Borland
complied application has the window focus or not.  If it is shown anywhere
on the screen the screen saver fails.  If the Borland compiled application
is not minimized but is completely covered by other windows applications,
the screen saver works properly.

3.  The window minimize button does not always operate.  I only see this bug
in one of the applications.  It appears to be impacted only when the
application is in a state when it is continually refreshing data within the
application.

4.  Other applications that are residing under the Borland complied
application do NOT properly display when the focus has been shifted to their
associated window.  The Borland application remains on top.  There are two
methods I can use to bring full focus to the desired application.  I can
either click on the other application's main titlebar area (only) to get it
on top (if the titlebar is visible) or I must minimize the Borland compiled
application.

Here are some environmental factors that may be impacting this situation:

1.  The video involved is a Matrox G400 (AGP) with the latest drivers
installed.  The version of the driver does NOT seem to matter though where a
variety have been used with the same effects noted.  The driver is quality
certified and has been around for quite a while.

2.  This machine is running with TWO processors.  I suspect this is probably
the main impacting factor associated with these bugs where there are not
that many people out there that have this configuration.

3.  Various versions of MSIE have been loaded on the machine and does not
impact the issue.  This issue has been evident for more than a year, so
there have been lots of windows update patches applied as well.

4.  This is a Windows 2000 OS machine.  Lots of stuff is running, but only
the Borland compiled applications are exhibiting this sort of behavior.

I have screen shots available for upload displaying the first problem noted
above.  I can also pass along the compiled program and associated dll's
(they are small).  I don't watch this newsgroup and it is not available from
my newsgroup provider, so I would appreciate any communication via email. I
can be contacted at jmelnet <at> usa.com.

Tim

.