CompuServe Thread

DOpus 4.0 buglet

10 messages in this thread
#52908From: Wayne ColeMar 17, 1993 2:30 AM
I called in a problem on DOpus 4.0: it was adding strange graphic chars to the comments of files as displayed in the list windows. Tech support suggested makingchanges on the operations/lists page to see if that reset the condition to normal. It didn't. However, by starting configure from scratch and looking at when the proble arose (it is not a proble in the default config) I found that turning on the Systems/Directories Use ExAll() option the problem appeared. Turning it off caused the comments to show correctly again. I have KS 37.175, WB 37.67 (2.04) on a A2000, 4.1 Motherboard, GVP 33 mhz 68030 Combo card. wmc – via Autopilot!
#52949From: Martin MurrayMar 18, 1993 12:12 AM
Hi Wayne. This bug has actually always been around; it is in fact a bug in the ExAll() routine in some versions of kickstart 2.0 (it returns comments as BSTRs instead of normal CSTRs like it is supposed to). You are right, turning ExAll() off will make the problem go away. Jon
#53004From: Wayne ColeMar 19, 1993 2:04 AM
Jon, Is ExAll() a ROM routine? i.e. will upgrading to 2.1 not help? (not that this is a big deal with me – I can EASILY live without it.) wmc – via Autopilot!
#53044From: Martin MurrayMar 19, 1993 11:37 PM
Hi Wayne, yes ExAll() is a ROM routine, but it might have been setpatched in 2.1, I'm not sure. ExAll() has many problems, the least of which is the comment problem, and my advice is not to use it at all anyway. There's no actual benefit gained in using it under the v37 filesystem anyway. Jon
#53076From: Wayne ColeMar 21, 1993 5:03 AM
Jon, Thanks. I turned ExAll() off and am quite happy that way. No biggy. BTW, as I told your phone support people, your manual is one that should serve as an example of how manuals should be done. With only one minor point that you already had found, it is accurate, concise, but has detailed information fo the first time user and nice reference info for the frequent user who needs info on a prat he/she uses less frequently. And in addition to a great manual, it is a great program. I do have one suggestion, though. On the printer routine, I think it would be more useful to let the text style (bold etc) apply to header and footer as well as the text body. wmc – via Autopilot!
#53079From: Martin MurrayMar 21, 1993 9:29 AM
Hi Wayne. Thanks for your compliments on the manual, it is entirely due to the hard work of Eddie and Cash (and probably others) at Inovatronics. Regarding the printer routine, the text style actually ONLY applies to the header and footer; text body is printed in plain style. Jon
#53310From: Wayne ColeMar 25, 1993 4:51 AM
Jon, Well, the way you statedi t is the way I would perfer it actually. However the manual (p 70) states that "…this button allows you to modify the appearence of all the printed text except the headers and footers…" That is only the second errata I've noted for the docs (the first being the default directory for the CNFG file). That still does not lessen my opinion of the docs. Hey – maybe you guys can contract to do ASDG's docs :^} wmc – via Autopilot!
#53399From: Martin MurrayMar 26, 1993 9:40 PM
Hi Wayne, I hadn't noticed that the manual said that, I will make a note to Eddie of the error. Jon
#53480From: Wayne ColeMar 28, 1993 12:11 AM
I had a problem with the Opus printer command. I had a file selected, hit the printer button and the printer requester came up. It was properly filled in with my Prefrences settings. I then selected information for the header, footer and set the margins for 8 and 96 which should give me a 2/3" left margin and a 1/2" right margin at elite size. I got a 1-3/8" margin on the left and a 5/8" margin on the right. Then the routine added one line to the first page causeing the page number (footer) to comeout on the second page and a form-feed to be issued (got a page with just the word "Page" at the top right corner. The next page got everything on the page, but it only printed the word "Page" at the bottom of the page. The number hit the bit-bucke on the right, I guess. then page two was followed by a blank page, then page three printed with the same problems as two, and a blank page followed. On the last page (which was only a half page) no footer was printed but the printer form feed light was left on (a signal that there is still data in the buffer). I took it off line, pressed the FF button and got a blank page with the word Page in the upper right corner. I have a B2000 with GVP Combo 30 acc, HP LaserJet IIP printer. wmc – via Autopilot!
#53103From: Dominick J. FontanaMar 22, 1993 4:31 AM
Hi Wayne, I agree with you that DOpus 4.0 is a great program. However, I don't think the manual should serve as an example of how manuals should be done. I don't know which minor point you mean that has already been found, but I found the manual to be incomplete. What was there was pretty good, but too much was left out. For instance, the information provided on the internal commands and on how to actually add your own functions to DOpus was totally inadequate. I am a prior DOPus user, so I didn't have any trouble with it. But I think a first time user of the program would have a lot of trouble configuring their own custom buttons and menus. Also, the manual didn't mention the built-in Help files at all or how you can change them. This info was in the prior manual. It also didn't mention that the .CLA file holds the Classes for DOpus. So, yes, the program is excellent, but I think the manual could be improved. More time should be spent explaining how to actually write your own commands and functions. Dom Fontana –> Sent from NY via AP <–