View Single Post
Old 13 December 2012, 13:50   #2
Toni Wilen
WinUAE developer
 
Join Date: Aug 2001
Location: Hämeenlinna/Finland
Age: 49
Posts: 26,545
Quote:
Originally Posted by mark_k View Post
First a minor issue with the status bar track display. (I mentioned this in another thread but only by editing my post, so maybe you missed it.) Boot a demo which kills the system so trackdisk.device doesn't step the heads. Wait until demo loads and disk activity stops. Change graphics API. The floppy drive track indicators are blank. The indicators are only refreshed when the drive is next accessed. The same happens if you start with borderless window then change to standard.
I noticed but this is another after 2.5.1 stuff.


Quote:
A couple of suggestions related to window sizing. Currently WinUAE behaves differently with respect to window sizing for native chipset (including A2024) versus RTG modes. For native modes WinUAE uses the user-specified window size. If that is larger than the native mode in use, the native display is centred in the larger window. For RTG modes WinUAE always resizes the window to match the RTG mode size. The window reverts to the user-specified size when a native mode screen is next shown.
Tick "Scale if smaller option" in Expansion panel?

Quote:
Suggestion 2: Add an option to make A2024 modes behave like RTG modes with respect to automatic window sizing. So if the window size is 720x568, with auto-sizing enabled the size would increase to 1024x800/1024 when an A2024 mode becomes active, just like RTG modes. [At the moment the user has to manually increase window size to show the whole A2024 display.]
From emulation point of view it is chipset mode and chipset modes don't have "size" or "resolution". It needs extra hacks. Possible later.
Toni Wilen is offline  
 
Page generated in 0.07230 seconds with 11 queries