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.
Now Eliot Miranda asked me about launching Squeak on his mac and having it show up as full screen on the secondary display. Which of course does not happen since it opens on the main display and goes to full screen there. To do this I would need to know that I have to place the window on the secondary display, or elsewhere in the coordinate system which would be the secondary display, then go to full screen.
I'd like to propose that we grab another 4 bytes (8 bytes?) out of the header and store the top/left in mmm macintosh quickdraw coordinate systems values. Then on main window open a VM would need to see if the window created based on the top/left be visible, if so to open it at those coordinates, otherwise fall back to the historical code. I realize of course this might not work for Xwindows or Windows (no clue) but even just having the ability to position a squeak window at startup at a given location is more useful than our fall back position of 44 & 8.
Perhaps even suggesting a number (2) meaning use the secondary screen or something, mm and top/left being 0/0 of top/left of 2nd screen.
Thoughts? Well one part is do we need this? The second is how to implement in a manner that all VMs would do the right thing based on some magic numbers.
-- ======================================================================== === John M. McIntosh johnmci@smalltalkconsulting.com Corporate Smalltalk Consulting Ltd. http://www.smalltalkconsulting.com ======================================================================== ===
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 -- tim Rowledge; tim@rowledge.org; http://www.rowledge.org/tim Strange OpCodes: IXM: Initiate X-rated error Messages
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.
Hear, hear.
-C
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 3.9 too.
mmm one thing we don't have is access to window (1) which by default is the window opened by the vm... Lets see
hwp := HostWindowProxy new. hwp windowHandle: 1. "create this accessor" hwp on: Display. hwp windowPosition: 100@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
tim Rowledge; tim@rowledge.org; http://www.rowledge.org/tim Strange OpCodes: IXM: Initiate X-rated error Messages
-- ======================================================================== === John M. McIntosh johnmci@smalltalkconsulting.com Corporate Smalltalk Consulting Ltd. http://www.smalltalkconsulting.com ======================================================================== ===
vm-dev@lists.squeakfoundation.org
-
Craig Latta -
John M McIntosh -
tim Rowledge