Re: "set bounds" and unexpected vertical offset
Re: "set bounds" and unexpected vertical offset
- Subject: Re: "set bounds" and unexpected vertical offset
- From: "Tom Harrington" <email@hidden>
- Date: Tue, 17 Jul 2007 10:37:08 -0600
On 7/16/07, Doug McNutt <email@hidden> wrote:
Terminal.app has a tough time setting window bounds. I was once told that you have to do everything twice but even that isn't always enough.
I am now asking Terminal to set window bounds and then checking to see what it did. Only when I get the right answer back do I exit the loop.
<ftp://ftp.macnauchtan.com/Software/Progress/tViewInit>
for an example.
I've heard that too, but in this case I don't think that's the
problem. Repeating the "set" 50 times or so didn't make any
difference in the result.
And Terminal may adjust for font size but I see no evidence of it. The unit of measure is always pixels in bounds lists and if you change the font the window doesn't change size. Perhaps it's that I use proportional fonts for my coding.
I've seen Terminal doing that. You can set the size in pixels, but
the actual size may be slightly off to account for character width and
line height. It's not surprising if setting bounds and then
immediately getting bounds shows a slight difference, but again only
by a few pixels.
And. . . For arranging monitors it's best to be sure there is some phosphor at the upper left corner of the rectangle that encloses all monitors - gworld. For Apple it doesn't matter but if you play with X11 and Xinerama you can discover that "windows" get opened where you can't see them near the upper left corner of gworld.
Phosphor? That's what we used to have before LCD monitors took over, right?
--
Tom Harrington
email@hidden
AIM: atomicbird1
_______________________________________________
Do not post admin requests to the list. They will be ignored.
AppleScript-Users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
Archives: http://lists.apple.com/archives/applescript-users
This email sent to email@hidden