Smalltalk › Cincom › VisualWorks

[VW7.4] [unix bsd apple Power MacOSX] Screen default bounds answers -1280@0 corner: 1680@1050 ??

_‹ Previous Topic Next Topic _›

Classic

List

Threaded

3 messages Options

Stew MacLean

[VW7.4] [unix bsd apple Power MacOSX] Screen default bounds answers -1280@0 corner: 1680@1050 ??

When establishing my initial Window size in relation to the screen size, I’m getting:

Screen default bounds answering

-1280@0 corner: 1680@1050.

The negative x coordinate is rather strange, and throws my calculations.

Given that Windows is bypassing the getScreenDimensions primitive (see below), I’m wondering if there is a problem with this on the MacOSX as well.

I’d appreciate it if anyone could tell me if they have encountered this on the Mac, and what the workaround is? The obvious thing is to set the origin to 0@0, but I’m uncertain as to whether the bounds are actually correct.

The other thing that could be causing this is that she has an external screen plugged in. So maybe the primitive is getting confused by this?

Cheers,

Stewart

Screen>>eventDisplayChange: event

"Use this code on the Windows platform in place of #installBoundingBox in order to recompute the screen boundingBox and the subRegions. The primitive used in #getScreenDimensions fails to give the new dimensions"

Thomas Brodt

RE: [VW7.4] [unix bsd apple Power MacOSX] Screen default bounds answers -1280@0 corner: 1680@1050 ??

Maybe the default screen is the right one which has 0@0 as origin. The left one is added to the left and so gets negative x
coordinates?
Just a thought.

Thomas

> -----Original Message-----
> From: Stewart MacLean [mailto:[hidden email]]
> Sent: Wednesday, April 11, 2007 1:28 AM
> To: [hidden email]
> Subject: [VW7.4] [unix bsd apple Power MacOSX] Screen default
> bounds answers -1280@0 corner: 1680@1050 ??
>
> When establishing my initial Window size in relation to the
> screen size, I'm getting:
>
> Screen default bounds answering
>
> -1280@0 corner: 1680@1050.
>
> The negative x coordinate is rather strange, and throws my
> calculations.
>
> Given that Windows is bypassing the getScreenDimensions
> primitive (see below), I'm wondering if there is a problem
> with this on the MacOSX as well.
>
> I'd appreciate it if anyone could tell me if they have
> encountered this on the Mac, and what the workaround is? The
> obvious thing is to set the origin to 0@0, but I'm uncertain
> as to whether the bounds are actually correct.
>
> The other thing that could be causing this is that she has an
> external screen plugged in. So maybe the primitive is getting
> confused by this?
>
> Cheers,
>
> Stewart
>
>
>
> Screen>>eventDisplayChange: event
> "Use this code on the Windows platform in place
> of #installBoundingBox in order to recompute the screen
> boundingBox and the subRegions. The primitive used in
> #getScreenDimensions fails to give the new dimensions"
>

Martin McClure

Re: [VW7.4] [unix bsd apple Power MacOSX] Screen default bounds answers -1280@0 corner: 1680@1050 ??

Thomas Brodt wrote:
> Maybe the default screen is the right one which has 0@0 as origin.
> The left one is added to the left and so gets negative x
> coordinates? > Just a thought.

Yes.

As far as I know, the Mac has always used 0@0 as the upper left corner
of the screen with the menu bar. If there is another screen above or to
the left of this screen, some coordinates will be negative.

Regards,

-Martin