You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've recently (this month) had cause to look at the plugin and noticed that the conversion from python2 to python3 didnt work too well. There were certain python3 issues that were not seen at python2 such as segmentation faults when using process stuff under threads (apparently a bad idea in python3).
There are other instabilities I've noted - other segmentation faults randomly seen - I've seen RB crashing when just activating the plugin.
This is probably again something to do with the threads use on activate.
Thus the plugin needs to be stabilised first before nice GUI touches such as this issue will get a look-see.
just found out that the plugin was downloading the radio listings from icecast and the community-board everytime rhythmbox was launched and the plugin activated.
This has been fixed in the latest commit.
I've been looking at the magnatune plugin. There is a nice piece of code that gives a progress bar when actually downloading the radio listings files. I'll have a look to see if this will work for this plugin.
From a usability aspect, the fact that the plugin takes a very long time to load stuff is worrying.
However, we should really give some proper feedback for the user. At the moment stuff is tucked away in the statusbar.
We should really use RB.TaskProgressSimple (https://lazka.github.io/pgi-docs/#RB-3.0/classes/TaskProgressSimple.html) in the following slow areas:
Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.
The text was updated successfully, but these errors were encountered: