CompuServe Messages

A bug thread is a good idea, Brian! Here's what I've noticed so far. 1. A persistent bug in all versions to date: "list s" does not work from the CLI. "list s/" or "list s:" or "list :s" does. 2. ScrollLayers() was fixed in pt. When writing to an Intuition, GimmeZeroZero window in a workbench screen with a superbitmap larger than 640 pixels wide, Text() now will write lines longer than 640 into the superbitmap (unlike versions 1.2 beta 2 and 1.1). But if the text line crosses the 640 boundary, a few characters on either side of the boundary are smeared. Characters further beyond the boundary come out okay. (This is revealed by scrolling with ScrollLayers(). I am pretty certain that ScrollLayers() is not the problem.) The nature of the smearing depends on the window options. For example, if I make the window BORDERLESS!SIZEBBOTTOM, then ALL characters to the left of about 640 in a line longer at are okay. I suspect Text() is still buggy, but it may be something else. ClearEOL() still will not clear the superbitmap beyond 640 in windows like the above. It apparently has the same bugs as before. I worry about this, because I have not done systematic checks of other graphics functions writing across the 640 boundary in that kind of window, nor have I checked what happens at the 200 erbitmap. 3. Neither the Epson nor the Epson JX-80 driver recognizes the letter quality mode for the PRT: device set in preferences, when used with an Epson FX-80. Surely the FX-80 is THE standard Epson, and nearly THE standard printer?! 4. As we all know, the CLI does not include line editing on the command line, except for backspaces. I for one vote to classify that as a bug, in a machine of AMY's quality. 5. DiskDoctor in the toolkit does not recover valid data blocks on a track with any garbaged data–at least that's my interpretation of why it throws away uncorrupted files. 6. Clicking on the "searching for fonts" message on the workbench freezes the system. That's all for now. –David