MetaCard List Digest Tuesday, October 24 2000 Volume 04 : Number 017 ---------------------------------------------------------------------- Date: Sun, 22 Oct 2000 17:56:41 +0100 From: Kevin Miller <[EMAIL PROTECTED]> Subject: Re: windowBoundingRect On 23/10/00 5:21 am, "Raymond E. Griffith" <[EMAIL PROTECTED]> wrote: > I would like to comment on this feature, which is described in the docs this > way: > > The global "windowBoundingRect" property specifies the rectangle in > which all windows must open. By default it is the same as the > screenRect minus the size of the menubar (on Mac) or task bar (on > Windows), but can be made smaller to support UI features like tool > bars. > > This property now makes it exceedingly difficult to print full pages if your > screen is set to, say, 800 x 600. The windowBoundingRect is 0,20,640,480. > > I believe this property, while meant to be a good feature, is a bad idea. > > I have a stack I have created to hold formatted data for printing. The rect > of the stack is -- or *was* -- 468 x 648. This is the printing area of a > letter sized sheet of paper with an inch margin all around. MC 2.3.2 now > consistently cuts this off, and will only open it to 468 x 546. This cuts > out nearly 1 1/2 inches of printable area from my page. > > This never happened in 2.3.1, but the windowBoundingRect was not a feature > there. So this is no bug. But it is annoying. > > I have found a workaround, although it is not always consistent yet. > > lock messages > open stack "Letter" > set the height of stack "Letter" to 648 > print card 1 of stack "Letter" > close stack "Letter" > > Scott, I know you meant well. But is there any chance of making this > property optional? Say, setting the windowBoundingRect to empty turns it > off, or something? I'm afraid that others will find they are not getting all > of their printouts as well. It doesn't apply to palettes, and it doesn't apply if you set the rect of the stack on preOpenStack - either of these can be used. But turning it off isn't a good idea, your stacks could open too large for the current screen or under a toolbar. Regards, Kevin Kevin Miller <[EMAIL PROTECTED]> <http://www.runrev.com/> Runtime Revolution Limited (formerly Cross Worlds Computing). Tel: +44 (0)131 672 2909. Fax: +44 (0)1639 830 707. ------------------------------ Date: Sun, 22 Oct 2000 15:30:38 -0600 (MDT) From: Scott Raney <[EMAIL PROTECTED]> Subject: Re: windowBoundingRect On Sat, 21 Oct 2000 "Raymond E. Griffith" <[EMAIL PROTECTED]> wrote: > I would like to comment on this feature, which is described in the docs this > way: > > The global "windowBoundingRect" property specifies the rectangle in > which all windows must open. By default it is the same as the > screenRect minus the size of the menubar (on Mac) or task bar (on > Windows), but can be made smaller to support UI features like tool > bars. > > This property now makes it exceedingly difficult to print full pages if your > screen is set to, say, 800 x 600. The windowBoundingRect is 0,20,640,480. > > I believe this property, while meant to be a good feature, is a bad idea. > > I have a stack I have created to hold formatted data for printing. The rect > of the stack is -- or *was* -- 468 x 648. This is the printing area of a > letter sized sheet of paper with an inch margin all around. MC 2.3.2 now > consistently cuts this off, and will only open it to 468 x 546. This cuts > out nearly 1 1/2 inches of printable area from my page. > > This never happened in 2.3.1, but the windowBoundingRect was not a feature > there. So this is no bug. But it is annoying. > > I have found a workaround, although it is not always consistent yet. > > lock messages > open stack "Letter" > set the height of stack "Letter" to 648 > print card 1 of stack "Letter" > close stack "Letter" Setting the rect in a preOpenCard or preOpenStack handler also always overrides the WBR setting. > Scott, I know you meant well. But is there any chance of making this > property optional? Say, setting the windowBoundingRect to empty turns it > off, or something? I'm afraid that others will find they are not getting all > of their printouts as well. How about this property be ignored if the formatForPrinting property of the stack is set to true? That should always be the case if you're going to print it, and never the case if you're not... Scott > Thanks, > > Raymond ******************************************************** Scott Raney [EMAIL PROTECTED] http://www.metacard.com MetaCard: You know, there's an easier way to do that... ------------------------------ Date: Sun, 22 Oct 2000 17:18:34 -1000 From: Sivakatirswami <[EMAIL PROTECTED]> Subject: Sockets/FTP One File Has anyone put together a script that will open a socket and FTP a single file? I have Andu's FTP client, but the process is all broken out into different functions. If I could just see it all in one series of command lines in a single script that would help a lot to understand "the sockets thing." Hinduism Today Sivakatirswami Editor's Assistant/Production Manager www.HinduismToday.com www.HimalayanAcademy.com [EMAIL PROTECTED] ------------------------------ Date: Mon, 23 Oct 2000 08:52:49 -0700 From: "Geoff Canyon" <[EMAIL PROTECTED]> Subject: Is the list alive? and a question I haven't seen anything on the list in five days, so consider this a ping... Someday I'll stop asking stupid questions: is there a way to use the file system to copy (or move) a file from one place to another without opening it? I didn't see a copyfile command, the copy command doesn't seem to want to work, and and the rename command, while it seems documented to be able to move files (but not folders except on Unix) doesn't work for me either. I'm on a Mac, OS 9, MC 2.3.1. Thanks Geoff ------------------------------ Date: Mon, 23 Oct 2000 15:02:14 -0400 (EDT) From: andu <[EMAIL PROTECTED]> Subject: test Regards, Andu _______________________ [EMAIL PROTECTED] ------------------------------ End of MetaCard List Digest V4 #17 **********************************
