<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">On 19-Jan-19 3:55 AM, Axel Grude wrote:<br>
</div>
<blockquote type="cite"
cite="mid:560ee133-beb6-770c-586c-732fbaf5c88a@gmail.com">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<div id="smartTemplate4-template">
<p>Garrafrauns, 18/Jan/2019 17:22</p>
<p>Oooh - I didn't see there was a menu "by Add-on Status" - I
guess it would have been helpful to completely hide the
"disabled" data in the other graphs. There is really no good
way to get the users back (a disabled Add-on cannot notify you
about it's new features to convince you to enable it again, so
it pretty much useless for my metrics) <span
class="moz-smiley-s1"><span>:-)</span></span><br>
</p>
</div>
</blockquote>
My experience with TB60 Beta was that add-on's that had been
disabled for years re-enabled as new V60 versions became available.
So perhaps disabled is not a fatal as you suggest. While I did not
like this automatic reappearance, a "there is a new version of XXX
available" dialog would have been nice. I did not like it because I
install loads of add-ons for support issues and generally just
disable them when the support topic is done. Other might have
different views on the automatic re-enabling.<br>
<br>
<i>Matt</i><br>
</body>
</html>