This is Invisible-text-in-WriteNow,-...-bombing. in view mode; [Up]
Date: Sun 30-May-1990 21:35:09 From: Unknown Subject: Invisible text in WriteNow, ... bombing. During a recent WriteNow late-night essay-writing stint, I had 40 pages of document and I wanted to shrink it down a little. I selected the whole paper and changed the line height field in the ruler, just like normal. To my horror, My entire document "disappeared." It was apparently still there: I could "select" text that I couldn't see. Little rectangles of gray appeared in the window, but there was no text to be seen. Even the between-page black strips weren't there. After I tried fruitlessly to select this and that, WriteNow suddenly closed its windows and terminated. When I tried reopening them, it gave me the "File Busy" panel. Has anything like this happened to anyone else? By the way (I know you're all dying to know), I got the paper back fine, and was evenually able to make the change line height change. Jeff Adams adams@ucscl.ucsc.edu >From: jacob@gore.com (Jacob Gore)
Date: Sun 01-Jun-1990 02:04:55 From: Unknown Subject: Re: Invisible text in WriteNow, ... bombing. adams@jif.berkeley.edu (Jeffrey P. Adams) politely asks: > >... changed the line height field in the ruler, just >like normal. To my horror, My entire document "disappeared." > >Has anything like this happened to anyone else? As a matter of fact, just yesterday I was finishing up a 40+ page document when this happened -- everything went blank, then 30 seconds later, WriteNow died. Unfortunately, I forgot to look for console messages. I, like you, was changing the line height when this happened. Frequent saves of the document reduce losses, since a copy of the busy document may be opened. (Luckily I save very frequently & lost little.) Perhaps this bug report got lost with the one entitled "No Underlining Supported." :-)
Date: Sun 01-Jun-1990 03:53:05 From: Unknown Subject: Re: Invisible text in WriteNow, ... bombing. In article <2665cd47.3a7a@petunia.CalPoly.EDU> dstaas@polyslo.CalPoly.EDU ((That's two a's)) writes: > > >adams@jif.berkeley.edu (Jeffrey P. Adams) politely asks: >> >>... changed the line height field in the ruler, just >>like normal. To my horror, My entire document "disappeared." >> >>Has anything like this happened to anyone else? > >As a matter of fact, just yesterday I was finishing up a 40+ page document >when this happened -- everything went blank, then 30 seconds later, WriteNow >died. Unfortunately, I forgot to look for console messages. I, like you, >was changing the line height when this happened. > I've had WriteNow just up and vanish on me in the middle of typing. This has happened several times, including once as I was about half-way through doing a three-hour exam :-(. Thank god for an understanding prof. I've noticed that often the side of my left hand accidently depresses the left Alternate key, converting subsequent keystrokes into alt sequences. I've hypothesized that there is some undocumented alt-key sequence which causes WriteNow to quit without further ado. Whatever the reason, WriteNow is number 1 on my ``Top 10 Things I Like Least on the NeXT machine''. I believe it is the main reason people perceive the machine as slow. What a pity so much of the documentation is in WriteNow. -glen diener grd@cm-next-9.stanford.edu >From: eps@toaster.SFSU.EDU (Eric P. Scott)
These are the contents of the former NiCE NeXT User Group NeXTSTEP/OpenStep software archive, currently hosted by Marcel Waldvogel and Netfuture.ch.