2012-07-17, 04:12
(2012-07-17, 03:26)chris295 Wrote: I was just about to post about this same issue. Yes, using the same resolution as XBMC will fix this, but it's not always practical. Some programs look really bad at higher resolutions. I was wondering if it's possible to include in the AutoIt launcher for the program which is having this problem a code to change the resolution back to 1920x1080 before launching or resuming XBMC again.
You can use the small freeware Display Changer to force the resolution change. Simple command line :
Code:
dccmd.exe -width=1920 -height=1080
must do the trick.
(2012-07-17, 03:26)chris295 Wrote: That's actually a really good idea. Can you give an example as to how I should write the code to check against two processes as well as which process to check for. Since every program I launch from Advanced Launcher has it's own AutoIt Launcher, it's not just one process. Is there a way to check against all AutoIt.exe's?
To simplify the code you just have to use different Advanced launcher autoit scripts with the same file name (for example launcher.exe). Then your script content will be :
- Activate TaskBarHider and nomousy
- Start XBMC
- Go into an infinite while loop until XBMC.exe and launcher.exe processes are closed (it is only the case when XBMC is closed when no not running any emulator/autoit script). Code could be :
Code:...
While (ProcessExists("XBMC.exe") AND ProcessExists("launcher.exe"))
Sleep(100)
WEnd
...
- Deactivate TaskBarHider and nomousy
- Restart XBMC