(2013-06-12, 18:13)dugan26 Wrote: perfect- I am somewhat familiar with the process - I followed your instructions about a year ago and worked like a champ.

Thanks again

Just to be 100% i have a launchers.xml in two spots

Documents\userdata\addon_data\plugin.program.advance.launcher
and
AppData\Roaming\XBMC\userdata\addon_data\plugin.program.advance.launcher

which one is the one i need?

Quote:When programs start stealing focus, they "pop up" in front of the window that you're currently viewing. A default setting in Windows prevents this from happening. If programs are stealing focus from your current window then this setting has been changed.

Follow the instructions below to stop this from happening for good.

Note: Changes to the Windows Registry are made in these steps. Take great care in making only the changes described below. I recommend that you backup the registry keys you're modifying in these steps as an extra precaution.


Here's How:

Click on Start and then Run.

In the text box in the Run window, type regedit and click OK. This will open the Registry Editor program.

Locate the HKEY_CURRENT_USER folder under My Computer and click on the (+) sign next the folder name to expand the folder.

Continue to expand folders until you reach the HKEY_CURRENT_USER\Control Panel registry key.

Select the Desktop key under Control Panel.

On the right-hand side of the screen, locate and double-click on the ForegroundLockTimeout DWORD.

In the Edit DWORD Value window that appears, set the Value data: field to 30d40.

Note: Make sure the Base option is set to Hexadecimal when entering the DWORD value.

Click OK and then close Registry Editor.

Reboot your PC for the changes you made to take effect.

From this point forward, programs should no longer steal the focus from the window that you're currently working in.

(2013-06-12, 20:51)jaydash Wrote: Kinda related to Advanced Launcher, I promise...

After starting up XBMC on Windows 7 something steals focus away after 30 seconds or so. I've created an ALT-Tab button on my remote to get around the problem, but it's annoying. I found the instructions below which detail a registry fix to prevent this from happening... thought it might be a more permanent solution, as opposed to fixing whatever is currently stealing focus, only to have something new pop up...

And here's how it's Advanced Launcher related! MY question/concern is simply: would this mess up/interfere with anything Advanced Launcher related? I use AL for launching into WMC's Netflix app and for launching PC games and console emulations. AL is a huge part of any good XBMC HTPC setup, so can't risk breaking it!

Quote:When programs start stealing focus, they "pop up" in front of the window that you're currently viewing. A default setting in Windows prevents this from happening. If programs are stealing focus from your current window then this setting has been changed.

Follow the instructions below to stop this from happening for good.

Note: Changes to the Windows Registry are made in these steps. Take great care in making only the changes described below. I recommend that you backup the registry keys you're modifying in these steps as an extra precaution.


Here's How:

Click on Start and then Run.

In the text box in the Run window, type regedit and click OK. This will open the Registry Editor program.

Locate the HKEY_CURRENT_USER folder under My Computer and click on the (+) sign next the folder name to expand the folder.

Continue to expand folders until you reach the HKEY_CURRENT_USER\Control Panel registry key.

Select the Desktop key under Control Panel.

On the right-hand side of the screen, locate and double-click on the ForegroundLockTimeout DWORD.

In the Edit DWORD Value window that appears, set the Value data: field to 30d40.

Note: Make sure the Base option is set to Hexadecimal when entering the DWORD value.

Click OK and then close Registry Editor.

Reboot your PC for the changes you made to take effect.

From this point forward, programs should no longer steal the focus from the window that you're currently working in.

(2013-06-12, 22:51)styx06 Wrote: Need some help launching spotify in combination with openbox.
I have created a script with the following content:

Code:

#!/bin/bash

openbox &
/usr/bin/spotify &
/usr/bin/spotcommander

killall -9 openbox

This should open spotify and spotcommander in seperate windows right?
Individual applications are installed properly....
When I try to run the script however from the launcher, nothing happens...any idea on how to fix this?

(2013-06-13, 01:29)Androider Wrote: Is it possible to use Advance Launcher on Android??
To either launch roms or apps??

(2013-03-24, 18:10)Angelscry Wrote: Ok... I have finally fix the problem:

• Install last Frodo XBMC version (12.1).
  
• Make this modification : http://forum.xbmc.org/showthread.php?tid=152866&pid=1372385#pid1372385. But instead of modifying the /etc/asound.conf file, do it with your ~/.asoundrc file.
  
• Then, if your DHDMI is directly plugged to the TV (like for me), setup XBMC audio settings like this :
  
  
  

(2013-06-14, 00:34)styx06 Wrote:

(2013-03-24, 18:10)Angelscry Wrote: Ok... I have finally fix the problem:

• Install last Frodo XBMC version (12.1).
  
• Make this modification : http://forum.xbmc.org/showthread.php?tid=152866&pid=1372385#pid1372385. But instead of modifying the /etc/asound.conf file, do it with your ~/.asoundrc file.
  
• Then, if your DHDMI is directly plugged to the TV (like for me), setup XBMC audio settings like this :
  
  
  

Could you help me out again
I am launching Spotify for Linux via the App Launcher but get no sound. Whe n applying your above fix however, Spotify will not playback at all anymore and will give me an error: "There is a problem with the connection to Spotify. Please try again shortly"

As soon as I remove the .asoundrc file and reboot, playback starts, albeit without sound. Any suggestions on how to fix this?

(2013-06-14, 08:33)styx06 Wrote: Already tried that, also disabled the GUI sounds, but getting the same message...

(2013-06-14, 15:32)styx06 Wrote: Yes, especially because searching tracks works normally, and if I delete the .asoundrc file and reboot, I see the player starting (time is running) and the message is gone. but no sound....