Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: utzoo!utcsri!utegc!utai!garfield!john13 From: john13@garfield.UUCP Newsgroups: comp.sys.amiga Subject: Window limits in Interlaced Workbench (Scribble) Message-ID: <3459@garfield.UUCP> Date: Mon, 9-Feb-87 15:46:31 EST Article-I.D.: garfield.3459 Posted: Mon Feb 9 15:46:31 1987 Date-Received: Tue, 10-Feb-87 06:38:35 EST Organization: CS Dept., Memorial U. of Newfoundland, St. John's Lines: 62 Keywords: darn darn darn heck Summary: looking for patch to scribble executable [] Yesterday I got to thinking about some of the uses of Workbench interlace under 1.2. I tried Scribble 1.0 in 640X400, but the window _limits_ were set to 640X200! Now, I'm all for bigger and better machines and everything, but Scribble is my favourite Amiga wordprocessor (although I like Professional Text Engine better for plain text), and it won't allow me to do something that the C-128 can do (yes, Pocket Writer II allows you to do WYSIWYG editing in 640X400, don't ask me how)! ** Can anyone come up with a patch to change the "200" in the window structure definition to a "400"? Would resizing the window be likely to break the program (it seems to me that it shouldn't)? In a more general fashion, how difficult would it be to grep an executable for a particular string (the title of a screen, window, or menu item), and then locate pointer references to that string? I can imagine a display screen with something like struct Window Window = { }; Wish to change parameter (y/n)? The labelled parameters in the structure declaration should make it clear whether or not it is actually the right spot in the code, or just a random integer that happens to be a pointer to the string, ie if the top edge is at 0xffff, 0x4232 you know you need to look farther on. This might be helpful for cutting down the # of bitplanes in some of those applications using custom screens, moving poorly placed submenu hit boxes, etc. But since I'm not familiar with the format of executable files, I'll leave that to some other enterprising soul (perhaps the authors themselves, or beta tester with source?). -------------- Since we are soon to see an improved printer.device (what? you mean I can't quote you guys on that?), if anyone does write a skeleton driver to intercept calls to the printer.device, one of the nice things that I would like to see added is the redirection of a print job (control codes and all) to a file, maybe under a standard name like "capture:logfile", with capture: being a re-assignable directory. The chances of my getting a laser printer within 10 feet of my Amiga are slim to none for the foreseeable future, but I do know of a few (and a couple of plotters also) that might be used if I only had some way to upload completed print files. There is already an ST utility to do this... ------------- I've seen recent messages announcing the return of mod.amiga.sources (under a variety of different names). Now, there have been some recent postings from mod.amiga, but none reaching here in the sources/binaries newsgroups. I was told that any that came in destined for uncreated newsgroups would be funnelled to the local "junk" newsgroup; I've been monitoring it, without success. Has anyone received any postings from these newsgroups (or under other newsgroup names) since #45?????? ------------- John