2011-02-06, 23:30
Version 1.1.0 : This new version of Advanced Launcher fix some bugs and improve XBMC process control for Windows users.
The commands System.ExecWait() and System.Exec() which where previously used specifically to start windows applications have been replaced by the subprocess.Popen() command. Now, the way to start applications is similar to Linux and OSX. The first consequence of this change, is that roms filenames containing coma are now supported. The control of XBMC state, when an application is launched still possible. It is now made by an included executable controller file. This controller allows to assign different states to the XBMC process:
Changelog
The commands System.ExecWait() and System.Exec() which where previously used specifically to start windows applications have been replaced by the subprocess.Popen() command. Now, the way to start applications is similar to Linux and OSX. The first consequence of this change, is that roms filenames containing coma are now supported. The control of XBMC state, when an application is launched still possible. It is now made by an included executable controller file. This controller allows to assign different states to the XBMC process:
- Normal: XBMC run normally. It is similar to the System.Exec() command.
- Low Priority: XBMC run but with a low priority. When the launched application is closed XBMC priority become again normal.
- Paused: XBMC is paused. When the launched application is closed XBMC is become again active. It is similar to the System.ExecWait() command.
- Closed: XBMC is closed. When the launched application is closed XBMC is restarted automatically.
Changelog
- Fix bug with romfilenames containing comas under Windows
- Rename XBMC Wait State to XBMC Process State under Windows
- Add Low priority and Close option for XBMC Process under windows