[Vm-dev] saving window top/left in the image,
and what does it mean?
John M McIntosh
johnmci at smalltalkconsulting.com
Wed Jan 24 01:10:32 UTC 2007
Oh sure make me work all weekend on Sophie, and I forget *all* about
Ffenstri, has to be your fault Tim. I mean that assumes there is
*any* interest in
Ffenstri you know, well I did repackage for 3.10, likely works under
mmm one thing we don't have is access to window (1) which by default
is the window opened by the vm...
hwp := HostWindowProxy new.
hwp windowHandle: 1. "create this accessor"
hwp on: Display.
hwp windowPosition: 100 at 100
I doubt closing window (1) would be a good thing to do, likely the
mac carbon VM will freak, must fix that...
ya, open squeak, use windowPosition: to put where you want window.
On Jan 23, 2007, at 2:39 PM, tim Rowledge wrote:
> On 23-Jan-07, at 2:26 PM, John M McIntosh wrote:
>> For reasons lost in time, although one of the readers might now,
>> the vm stores the window width/height in the image file, but not
>> the top/left.
> And a totally pointless thing that is too. There simply isn't any
> need to do it - especially with the Ffenstri code allowing easy
> access to setting the position/size/etc of the window(s). All this
> can be in the image startup code instead of buried pointlessly in
> the file header. We could query the screen size(s), decide sensibly
> where to locate the window, whether it can match the saved size or
> not, all that in the image with easily modified policy.
> I don't think we had secondary screen stuff specified as yet for
> Ffenestri but it is probably a trivial addition.
> tim Rowledge; tim at rowledge.org; http://www.rowledge.org/tim
> Strange OpCodes: IXM: Initiate X-rated error Messages
John M. McIntosh <johnmci at smalltalkconsulting.com>
Corporate Smalltalk Consulting Ltd. http://www.smalltalkconsulting.com
More information about the Vm-dev