Issue with executebuiltin ActivateWindow in Kodi 18
#1
I am now having an issue with the following commands, using the released version of Leia (Kodi 18), on Windows.  Latest version of Xonfluence 4.0.10 skin, but also tested in Estuary Skin.

These commands don't seems to pop up the screens I am trying to get:

The code I am using:

import xbmc
    xbmc.executebuiltin('ActivateWindow(screencalibration)')   - should popup the Screen calibration window.  It did on Krypton with version 3.x.x of Xonfluence.
    xbmc.executebuiltin("ActivateWindow(systemsettings)")   - should popup the System settings window.  It did on Krypton with version 3.x.x of Xonfluence.

Has something changed in the accepted format for Leia?

Any assistance would be greatly appreciated!

Cheers,
Ken
Reply
#2
nope, nothing changed.
check your Debug Log if any errors/warnings are logged.
Do not PM or e-mail Team-Kodi members directly asking for support.
Always read the Forum rules, Kodi online-manual, FAQ, Help and Search the forum before posting.
Reply
#3
Hmm, this is the error:


 Activating window ID: 10011
2019-02-16 22:25:42.830 T:3011150624    INFO: Activate of window '10011' refused because there are active modal dialogs
2019-02-16 22:25:42.831 T:2978997104    INFO: CActiveAESink::OpenSink - initialize sink
2019-02-16 22:25:42.831 T:2978997104   DEBUG: CActiveAESink::OpenSink - trying to open device ALSA:@:CARD=AMLM8AUDIO,DEV=0
2019-02-16 22:25:42.831 T:2978997104    INFO: CAESinkALSA::Initialize - Attempting to open device "@:CARD=AMLM8AUDIO,DEV=0"
2019-02-16 22:25:42.836 T:2978997104    INFO: CAESinkALSA - Unable to open device "sysdefault:CARD=AMLM8AUDIO" for playback
2019-02-16 22:25:42.838 T:2978997104    INFO: CAESinkALSA - Unable to open device "default:CARD=AMLM8AUDIO" for playback
2019-02-16 22:25:42.839 T:2978997104    INFO: CAESinkALSA::Initialize - Opened device "front:CARD=AMLM8AUDIO,DEV=0"
2019-02-16 22:25:42.840 T:2978997104    INFO: CAESinkALSA::InitializeHW - Your hardware does not support AE_FMT_FLOAT, trying other formats
2019-02-16 22:25:42.841 T:2978997104    INFO: CAESinkALSA::InitializeHW - Using data format AE_FMT_S16NE
2019-02-16 22:25:42.841 T:2978997104   DEBUG: CAESinkALSA::InitializeHW - Request: periodSize 4096, bufferSize 16384
2019-02-16 22:25:42.846 T:2978997104   DEBUG: CAESinkALSA::InitializeHW - Got: periodSize 4096, bufferSize 16384
2019-02-16 22:25:42.846 T:2978997104   DEBUG: CAESinkALSA::InitializeHW - Setting timeout to 372 ms
2019-02-16 22:25:42.846 T:2978997104   DEBUG: CAESinkALSA::GetChannelLayout - Input Channel Count: 2 Output Channel Count: 2
2019-02-16 22:25:42.846 T:2978997104   DEBUG: CAESinkALSA::GetChannelLayout - Requested Layout: FL, FR
2019-02-16 22:25:42.846 T:2978997104   DEBUG: CAESinkALSA::GetChannelLayout - Got Layout: FL, FR (ALSA: none)
2019-02-16 22:25:42.846 T:2978997104   DEBUG: CActiveAESink::OpenSink - ALSA Initialized:
2019-02-16 22:25:42.846 T:2978997104   DEBUG:   Output Device : AML-M8AUDIO
2019-02-16 22:25:42.846 T:2978997104   DEBUG:   Sample Rate   : 44100
2019-02-16 22:25:42.847 T:2978997104   DEBUG:   Sample Format : AE_FMT_S16NE
2019-02-16 22:25:42.847 T:2978997104   DEBUG:   Channel Count : 2
2019-02-16 22:25:42.847 T:2978997104   DEBUG:   Channel Layout: FL, FR
2019-02-16 22:25:42.847 T:2978997104   DEBUG:   Frames        : 4096
2019-02-16 22:25:42.847 T:2978997104   DEBUG:   Frame Size    : 4
2019-02-16 22:25:42.965 T:2478170992    INFO: Python interpreter stopped
2019-02-16 22:25:42.965 T:2478170992   DEBUG: Thread LanguageInvoker 2478170992 terminating
2019-02-16 22:25:42.971 T:2945426288   ERROR: GetDirectory - Error getting plugin://plugin.video.test/?action=setCalibrate
2019-02-16 22:25:42.971 T:2945426288   DEBUG: Thread waiting 2945426288 terminating
2019-02-16 22:25:42.977 T:3011150624   DEBUG: ------ Window Deinit (DialogBusy.xml) ------


Any thoughts on what that means?

Cheers,
Ken
Reply
#4
I actually found some info on a Google search.  If I add this line before, it works:

xbmc.executebuiltin('Dialog.Close(busydialog)')

Probably just a poor workaround, but hey it works for now.

Cheers,
Ken
Reply
#5
nah, that is the proper way.
any open dialogs must be closed before you can activate a new window.
Do not PM or e-mail Team-Kodi members directly asking for support.
Always read the Forum rules, Kodi online-manual, FAQ, Help and Search the forum before posting.
Reply
#6
Oh, OK thanks a million!

Cheers
Ken
Reply

Logout Mark Read Team Forum Stats Members Help
Issue with executebuiltin ActivateWindow in Kodi 180