(2019-12-08, 14:29)Wintermute0110 Wrote:

(2019-12-08, 14:16)il_sisco Wrote: Hi,

I have unistalled the old 0.9.7 and now i'm trying to install the new stable version 0.9.8, from scratch.

But when i try to create a new launcher (before i can choose the platform) i have this error:

ERROR: EXCEPTION Thrown (PythonToCppException) : -->Python callback/script returned the following error<--
                                             - NOTE: IGNORING THIS CAN LEAD TO MEMORY LEAKS!
                                            Error Type: <type 'exceptions.NameError'>
                                            Error Contents: global name 'AEL_platform_list' is not defined
                                            Traceback (most recent call last):
                                              File "/home/kodi/.kodi/addons/plugin.program.advanced.emulator.launcher/addon.py", line 37, in <module>
                                                main.Main().run_plugin()
                                              File "/home/kodi/.kodi/addons/plugin.program.advanced.emulator.launcher/resources/main.py", line 313, in run_plugin
                                                self.run_protected(command, args)
                                              File "/home/kodi/.kodi/addons/plugin.program.advanced.emulator.launcher/resources/main.py", line 405, in run_protected
                                                self._command_add_new_launcher(VCATEGORY_ADDONROOT_ID)
                                              File "/home/kodi/.kodi/addons/plugin.program.advanced.emulator.launcher/resources/main.py", line 1190, in _command_add_new_launcher
                                                sel_platform = dialog.select('Select the platform', AEL_platform_list)
                                            NameError: global name 'AEL_platform_list' is not defined
                                            -->End of Python script error report<--

Someone can help me?
Thank you

I think the problem is fixed in github, in the release-0.9.8 branch. Install that version and try.

As a workaround, use an XML to set up your launcher, that should work. Read carefully the first post to know about the XML configuration files. 

(2019-12-08, 14:45)il_sisco Wrote:

(2019-12-08, 14:29)Wintermute0110 Wrote:

(2019-12-08, 14:16)il_sisco Wrote: Hi,

I have unistalled the old 0.9.7 and now i'm trying to install the new stable version 0.9.8, from scratch.

But when i try to create a new launcher (before i can choose the platform) i have this error:

ERROR: EXCEPTION Thrown (PythonToCppException) : -->Python callback/script returned the following error<--
                                             - NOTE: IGNORING THIS CAN LEAD TO MEMORY LEAKS!
                                            Error Type: <type 'exceptions.NameError'>
                                            Error Contents: global name 'AEL_platform_list' is not defined
                                            Traceback (most recent call last):
                                              File "/home/kodi/.kodi/addons/plugin.program.advanced.emulator.launcher/addon.py", line 37, in <module>
                                                main.Main().run_plugin()
                                              File "/home/kodi/.kodi/addons/plugin.program.advanced.emulator.launcher/resources/main.py", line 313, in run_plugin
                                                self.run_protected(command, args)
                                              File "/home/kodi/.kodi/addons/plugin.program.advanced.emulator.launcher/resources/main.py", line 405, in run_protected
                                                self._command_add_new_launcher(VCATEGORY_ADDONROOT_ID)
                                              File "/home/kodi/.kodi/addons/plugin.program.advanced.emulator.launcher/resources/main.py", line 1190, in _command_add_new_launcher
                                                sel_platform = dialog.select('Select the platform', AEL_platform_list)
                                            NameError: global name 'AEL_platform_list' is not defined
                                            -->End of Python script error report<--

Someone can help me?
Thank you

I think the problem is fixed in github, in the release-0.9.8 branch. Install that version and try.

As a workaround, use an XML to set up your launcher, that should work. Read carefully the first post to know about the XML configuration files.  

Thank you!
I will try the very latest version.. 

(2019-12-07, 15:16)Wintermute0110 Wrote:

(2019-12-05, 22:49)Zastava Wrote: Thank you so much for the reply and explanation. That sounds like a great idea for future 0.10.0 release.
Can you tell me more regarding using a Kodi profile and special protocol? I confess that I read and tried using before special protocol together with sources, but got a little lost and didn't had effect on the relative art assets. I'm interested in trying that solution with a Kodi profile and let you know how it goes. How can I do it with a Kodi profile?

First have a look here. special://home in Linux points to directory /home/kodi/.kodi/ if your user name is kodi. Inside special://home you have the following:

Code:

$ ls -l /home/kodi/.kodi/
total 28
drwxr-xr-x addons
drwxr-xr-x media
drwxr-xr-x system
drwxr-xr-x temp
drwxr-xr-x userdata

addons is the directory where the addons are installed (Python source code for addons or XML files for skins, etc.). userdata is the directory where your user main profile is located. For example, addons store their data in subdirectories inside userdata.

OK, the first time you have to do is to find the directory pointed by special://home in your portable setup. Once you have located it, create a directory named for example AEL-assets. Then, place your assets:

Code:

/home/kodi/.kodi/AEL-assets/megadrive/icon.png
/home/kodi/.kodi/AEL-assets/megadrive/fanart.png
...

And then in AEL use the following:

Code:

special://home/AEL-assets/megadrive/icon.png
special://home/AEL-assets/megadrive/fanart.png
...

Note that Kodi accepts / as directory separator on both Unix and Windows.

I know this is not the best explanation in the world and also keep in mind that I'm sailing blind, I've never used a portable Kodi installation. However, I think this should work at least for launcher artwork. For ROMs artwork I'm not so sure at the moment. If you have more questions please ask.   

(2019-12-08, 17:23)il_sisco Wrote:

(2019-12-08, 14:45)il_sisco Wrote:

(2019-12-08, 14:29)Wintermute0110 Wrote: I think the problem is fixed in github, in the release-0.9.8 branch. Install that version and try.

As a workaround, use an XML to set up your launcher, that should work. Read carefully the first post to know about the XML configuration files.  

Thank you!
I will try the very latest version.. 

I realized that I was really using 0.9.9 alpha.. !!!

Now i get the -real- 0.9.8 stable release of 2 months ago, and i can create launchers..

The bug is in in:
https://github.com/Wintermute0110/plugin.program.AEL.git

(2019-12-09, 09:09)Wintermute0110 Wrote:

(2019-12-08, 17:23)il_sisco Wrote:

(2019-12-08, 14:45)il_sisco Wrote: Thank you!
I will try the very latest version.. 

I realized that I was really using 0.9.9 alpha.. !!!

Now i get the -real- 0.9.8 stable release of 2 months ago, and i can create launchers..

The bug is in in:
https://github.com/Wintermute0110/plugin.program.AEL.git

My mistake! I will fix 0.9.9 alpha ASAP. Recently I totally retrofitted the AEL platform information engine and there are a few regressions in the addon here and there.

(2019-12-10, 22:44)Bedwyr Wrote: There is a launcher I made for GoG Galaxy which updated to its 2.0 version today. I tried it out from within Kodi and noticed that GoG fails to exit when the window is closed and there is no setting to do so except from the Windows 10 system tray. That means that program focus is returned to Kodi, but that Kodi remains suspended because the GoG exe is still in memory. I thought that changing the launcher setting to be non-blocking would fix this, but that didn't happen. Barring CD Projekt adding a shutdown option to its Galaxy client, is there anything I can do with the AEL launcher to make sure Kodi regains control and isn't suspended when I close the Galaxy windows?

Thanks.

(2019-12-11, 07:41)Wintermute0110 Wrote:

(2019-12-10, 22:44)Bedwyr Wrote: There is a launcher I made for GoG Galaxy which updated to its 2.0 version today. I tried it out from within Kodi and noticed that GoG fails to exit when the window is closed and there is no setting to do so except from the Windows 10 system tray. That means that program focus is returned to Kodi, but that Kodi remains suspended because the GoG exe is still in memory. I thought that changing the launcher setting to be non-blocking would fix this, but that didn't happen. Barring CD Projekt adding a shutdown option to its Galaxy client, is there anything I can do with the AEL launcher to make sure Kodi regains control and isn't suspended when I close the Galaxy windows?

Thanks.

That looks like some GoG Galaxy regression and the best thing to do is to contact their support for help.

AEL is a multiplatform launcher which means it does not have Windows-specific code to control window behavior. There are utilities (Google a bit) you can use to control windows and processes from the command line. With such utilities, you can create a CMD of BAT file. In this thread there is information about such utilities. Use google with the parameter site:forum.kodi.tv to restrict the search to the forum only.   

(2019-12-11, 18:52)Bedwyr Wrote:

(2019-12-11, 07:41)Wintermute0110 Wrote:

(2019-12-10, 22:44)Bedwyr Wrote: There is a launcher I made for GoG Galaxy which updated to its 2.0 version today. I tried it out from within Kodi and noticed that GoG fails to exit when the window is closed and there is no setting to do so except from the Windows 10 system tray. That means that program focus is returned to Kodi, but that Kodi remains suspended because the GoG exe is still in memory. I thought that changing the launcher setting to be non-blocking would fix this, but that didn't happen. Barring CD Projekt adding a shutdown option to its Galaxy client, is there anything I can do with the AEL launcher to make sure Kodi regains control and isn't suspended when I close the Galaxy windows?

Thanks.

That looks like some GoG Galaxy regression and the best thing to do is to contact their support for help.

AEL is a multiplatform launcher which means it does not have Windows-specific code to control window behavior. There are utilities (Google a bit) you can use to control windows and processes from the command line. With such utilities, you can create a CMD of BAT file. In this thread there is information about such utilities. Use google with the parameter site:forum.kodi.tv to restrict the search to the forum only.   

Understood. I'll keep up with GoG development. Their new Galaxy client is actually really good (it'll ingest a bunch of game services cleanly; very clever acquisition of user data) compared to the old one. And this does look to be a feature they had but haven't implemented in the new client.

In the interim I've discovered Playnite. To other people trying to do what I'm doing--get UWP programs into a gamepad controllable launcher--this github open source software does a very good job of a fullscreen interface: playnite.link . One can just create an AEL launcher for that or, if they're ambitious, edit the Steam launcher add-on to accommodate Playnite (or GoG or whichever game aggregator is one's preference). I already use Steam and Launchbox. This may be my go-to for all other services including Epic and the XBox Game Pass.

(2019-12-12, 11:01)Wintermute0110 Wrote:

(2019-12-11, 18:52)Bedwyr Wrote:

(2019-12-11, 07:41)Wintermute0110 Wrote: That looks like some GoG Galaxy regression and the best thing to do is to contact their support for help.

AEL is a multiplatform launcher which means it does not have Windows-specific code to control window behavior. There are utilities (Google a bit) you can use to control windows and processes from the command line. With such utilities, you can create a CMD of BAT file. In this thread there is information about such utilities. Use google with the parameter site:forum.kodi.tv to restrict the search to the forum only.   

Understood. I'll keep up with GoG development. Their new Galaxy client is actually really good (it'll ingest a bunch of game services cleanly; very clever acquisition of user data) compared to the old one. And this does look to be a feature they had but haven't implemented in the new client.

In the interim I've discovered Playnite. To other people trying to do what I'm doing--get UWP programs into a gamepad controllable launcher--this github open source software does a very good job of a fullscreen interface: playnite.link . One can just create an AEL launcher for that or, if they're ambitious, edit the Steam launcher add-on to accommodate Playnite (or GoG or whichever game aggregator is one's preference). I already use Steam and Launchbox. This may be my go-to for all other services including Epic and the XBox Game Pass. 

If you use Launchbox as a frontend I'm very interested in your feedback in order to improve AEL. For example, things in Launchbox you love which are not in AEL, etc. 

(2019-12-13, 08:30)Wintermute0110 Wrote: @Jachin99 @Bedwyr Thanks both for your feedback, it's very important for me to hear other people's opinion.