View Single Post
Old 04-23-2018, 08:29 PM   #1491
davidfor
Grand Sorcerer
davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.
 
Posts: 24,905
Karma: 47303824
Join Date: Jul 2011
Location: Sydney, Australia
Device: Kobo:Touch,Glo, AuraH2O, GloHD,AuraONE, ClaraHD, Libra H2O; tolinoepos
Quote:
Originally Posted by sweth View Post
It looks like the issue is that the InterfaceActionBase class that the plugin is inheriting from sets can_be_disabled to False as the default:

Code:
class InterfaceActionBase(Plugin):  # {{{

    supported_platforms = ['windows', 'osx', 'linux']
    author         = 'Kovid Goyal'
    type = _('User interface action')
    can_be_disabled = False
Not sure why it has that as the default for UI plugins, when the API docs seem to warn against setting that to False, but allowing it to be disabled *should* be as simple as setting can_be_disabled back to True in __init__.py
I'll have a look, but I have a feeling I've seen a reason for them not allowing them to be disabled.

But, rather than randomly disabling plugins, it might be better to start a thread to discuss the problem you are having and see if anyone has ideas. Most of the user interface plugins will only do something when you interact with them. This one is a little different as it has hooks to do something when a device is plugged in or removed. But, that is about the only thing that disabling the plugin would affect.
davidfor is offline