From: John D. G. <jd...@di...> - 2012-09-10 03:23:32
|
On 2012-09-08 23:26, Stefan Frey wrote: > Starting place for Game Report: > Do you refer to the window position on the screen or the position of the > report inside the report window. The latter is wrong at startup of the > game, as it does not scroll to the bottom. I am under the impression > this did work in the past. Will have to check that. I'm referring to the position of the window on the screen. I am assuming that the content in the window is always upper left justified, with scrollbars if needed. > If it is the former: All window positions/sizes are saved automatically > after closing of Rails. I do not know what happens during the game at > resizes (does it resize to the latest saved position or does it resize > to the current status?) It seems to use the saved positions (even for a later playing of the same game) even though some of them are now off screen. It would be nice to have a "reset" ability, at least in configuration, but preferably usable in mid-game too. > For me the major annoyance is that windows that are on the second > monitor if I start Rails dual-heads. Next time I start up with only one > monitor, some windows will be completely hidden (as they are located > off-screen). I've never tried dual monitors on a Windows system. > So two possible remedies: > A) Provide an option to reset the window positions to some robust defaults). Yes. (The existing "cascade windows" option seems to work for all except the Report window.) > B) Check if a window is located on an invisible position and then move > that window back to the default (at least at startup). Auto-detecting this would be nice but probably not strictly necessary, unless the off-screen window is going to start causing exceptions to be thrown. |