- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
On my windows 2000 machine my array visualizer windows don't update when I resize them. I make extensive use of visualizer in my software using the fortran API's. When I resize an open plot window, the window changes dimension but a black band appears in the plot where the new window area is created.
Any ideas?
Any ideas?
Link Copied
5 Replies
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Same thing happens to me since I upgraded from 6.1A to 6.5A. I am going to report the problem to the support today.
Sabalan.
Sabalan.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Ditto for me.
Tom
Tom
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Please do report it to vf-support@compaq.com, and our Array Visualizer engineers will respond.
Steve
Steve
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
This is the answer that I got from vf-support:
" The "black border problem" is due to a bug in Microsoft's OpenGL
implementation for Windows 2000. We'll have a work-around to this problem implemented for Array Visualizer 1.6 (packaged with Visual Fortran 6.6) which will be out this Aug/Sept."
And I wrote back that there was no problem before I upgraded from AV 1.1A to AV 1.5A (CVF 6.1A to 6.5A).
Sabalan.
" The "black border problem" is due to a bug in Microsoft's OpenGL
implementation for Windows 2000. We'll have a work-around to this problem implemented for Array Visualizer 1.6 (packaged with Visual Fortran 6.6) which will be out this Aug/Sept."
And I wrote back that there was no problem before I upgraded from AV 1.1A to AV 1.5A (CVF 6.1A to 6.5A).
Sabalan.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
However, I can confirm that the described behavior occurs on my Windows 2000 machine and not on my Windows NT machine.
Tom
Tom

Reply
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page