OpenXTalk Forums

This is a totally Ka-Ka problem, and seems to happen, in my experience at least, if you have hooked up a lpatop (or a desktop) to 1 or 2 external monitors, dragged stacks over to them to give you more space to work, and then, at a later date, started up your machine without those monitors connected.
- -
For those of you who are into literary intextuality, the poem is from 'Alice Through the Needle's Eye' where the late, great Gilbert Adair almost outdid Lewis Carroll: it is, of course (!) a parody of 'The Sands Of Dee' by Charles Kingsley, the author of 'The Wind In The Willows and the starter of the Kingsley Races which, at least 50 years ago when my father taught there, were an annual thing at Wellington College.

https://www.poetrybyheart.org.uk/poems/the-sands-of-dee

richmond62 wrote: ↑Sat Nov 25, 2023 7:00 pm if you have hooked up a [laptop] (or a desktop) to 1 or 2 external monitors, dragged stacks over to them.., and then, at a later date, started up your machine without those monitors connected.

It probably remembers the position. If you open System preferences, displays, and choose 'Gather Windows', what then? You could of course set the location of the stack on openstack, and set it to item 3 of the screenrect / 2, item 4 of the screenrect /2

It probably remembers the position. If you open System preferences, displays, and choose 'Gather Windows',

It probably does, but several lazy slobs here and 'over there' cannot be bothered to do that and expect the IDE to do that for them.

I remember spotting something in my adventures of exploring old and dodgy LC code, that retains the position of each stack by name and ID when they are closed. This would explain why they are offscreen. There just needs to be a check somewhere to check if the window is within the rect of the main screen. (this will have the opposite effect though, that if you wanted your stacks to reappear on screen 2, they'd probably always default to screen 1 again). - better that than to not be able to see them.

This is the same story as the geometry manager bug. Having to set things in script (workarounds), that should not be issues in the first place.