comp.lang.idl-pvwave archive
Messages from Usenet group comp.lang.idl-pvwave, compiled by Paulo Penteado

Home » Public Forums » archive » Font problems with version 5.1 under win95
Show: Today's Messages :: Show Polls :: Message Navigator
E-mail to friend 
Switch to threaded view of this topic Create a new topic Submit Reply
Font problems with version 5.1 under win95 [message #11925] Sun, 31 May 1998 00:00 Go to next message
Brian Jackel is currently offline  Brian Jackel
Messages: 34
Registered: January 1998
Member
Greetings

We just last week got a great new PC (300 Mhz, 128 Mb RAM) for
analyzing a big data set. Life would be good, except that IDL
5.1 seems to step on the fonts. Specifically, after operating
for a while (5-30 minutes) the fonts in the log window get
corrupted, sort of like they're missing every other scan line.
Following that, _every_ font on the desktop starts to have the
same problem. The only cure I've found is to restart win95.

This is quite irritating.

The application isn't using widgets or object graphics or any-
thing fancy at all. I haven't been able to pin down a single
cause, but right now I'm just reading in a (smallish) text file
and playing around with plots at the command line.

Has anyone seen behaviour like this before, or have any
suggestions for a fix? All suggestions are welcome.


--
Brian Jackel
Re: Font problems with version 5.1 under win95 [message #11973 is a reply to message #11925] Thu, 04 June 1998 00:00 Go to previous message
mgs is currently offline  mgs
Messages: 144
Registered: March 1995
Senior Member
In article <6ksvf0$80o@ds2.acs.ucalgary.ca>, Brian Jackel
<jackel@danlon.physics.uwo.ca> wrote:

> Greetings
>
> We just last week got a great new PC (300 Mhz, 128 Mb RAM) for
> analyzing a big data set. Life would be good, except that IDL
> 5.1 seems to step on the fonts. Specifically, after operating
> for a while (5-30 minutes) the fonts in the log window get
> corrupted, sort of like they're missing every other scan line.
> Following that, _every_ font on the desktop starts to have the
> same problem. The only cure I've found is to restart win95.

I remember something similar a few years ago on a client's Windows 3.11
WfWG system. We were working with some pretty large files, also. The font
problem was not the same as you describe. We were seeing the specified
fonts turning into the generic system fonts after running for a while. One
thing that I recall from the application is that it was written very
sloppily by a student and chewed up memory relentlessly. Variables and
structures were unnecessarily copied several times which I'm sure played
havoc with memory, or at least exercised the hell out of it.

> This is quite irritating.
>
> The application isn't using widgets or object graphics or any-
> thing fancy at all. I haven't been able to pin down a single
> cause, but right now I'm just reading in a (smallish) text file
> and playing around with plots at the command line.

Our application was making a lot of use of graphics and widgets.

> Has anyone seen behaviour like this before, or have any
> suggestions for a fix? All suggestions are welcome.

Sorry, no suggestions other than changing the OS :-)

--
Mike Schienle Interactive Visuals
mgs@sd.cybernex.net http://ww2.sd.cybernex.net/~mgs/
  Switch to threaded view of this topic Create a new topic Submit Reply
Previous Topic: 16 bit grayscale tiff file
Next Topic: warning: (all(part1))(part2) = part2*0.

-=] Back to Top [=-
[ Syndicate this forum (XML) ] [ RSS ] [ PDF ]

Current Time: Wed Oct 08 13:31:12 PDT 2025

Total time taken to generate the page: 0.00501 seconds