I'm already committing myself to migrating from MameWAH to AM. As part of this I have setup dual-boot arrangements for the arcade PCs (basically XP64 for mameWAH based, Win7 for AM-based in future) I'm currently setting up. Another reason why I've put XP64 on these machines is CRT-emudriver compatability issues with older video cards (I'm using some old Radeon X300-X1050 video cards in them). But that is off-topic.
Cools: In terms of my use case for having AM, switch resolutions is not about convenience navigating the desktop. Rather, it is that I like to play some games (that aren't part of Groovymame, like PC games or WinUAE or whatever) in specific resolutions and I would like to be able to launch them from the frontend. One way to do this is to set the resolution at the frontend's platform-theme-page, then the game uses that resolution when you launch it. I haven't tested this with AM, but I can imagine there are a lot of games/platforms that won't want to run in 640x240, or won't look good in it anyway. I expect that some games will be fine but others will have problems.
Even if the games support stretched resolutions, sometimes I want to play games in modes with 256 or even 288 lines or whatever. Managing variable game resolution requirements within a single AM install that uses a single video mode now gets more complicated. Even taking this into account, I like to choose resolution for each platform's theme page. To make things even more funky, I like to use my frontend to do more than just play games.
For example, I also use MameWAH to launch music & video clips from my home collection. My wife loves having my cab in the living room of the house for this reason. For the videoclips (all low-res but good quality) I like to choose a low-res interlaced mode like 768x512 768x576. It looks great for video, but would look a bit "meh" for games! But I assume I'd have to settle for the one-resolution-that-rules-them-all in AM
So that is my usage case for AM autoswitching resolutions, but I don't expect that to happen soon.
A workaround is to launch an external app like "changecreenresolution.exe" from a pre-emulator command line to change the res before the game is launched (and a post-emulator command line to switch it back), but I haven't experimented with this enough to know if it is viable.
So those really are the issues for me with using AM - and, to a large extent, moving to Win7 too. Oh and that AM doesn't have a portable GUI-based layout designer (every TV/PVM I've worked on is a bit different in terms of viewable screen area and tolerance of different resolutions, and I always like to tweak my layouts in-situ for this reason).
Q: Can ArcadeOSD be launched from the command line with parameters to switch to a specific resolution? What would be ideal is to be able to do something like this as a pre-emulator command:
arcadeosd.exe -switchres 320x256@53