Sorry, I should've said, they're supposed to be displayed based on settings. There are like various modules, and I use Ace profiles along with Lib-DualSpec, so if your other spec (or just other profile, for that matter) doesn't use the same modules, their feeds are useless on the display addon.
Yeah, indeed. Preferrably it would be a "show/hide" field rather than "enable/disable". The display should not delete settings for the feed.
main reason this sort of thing wasnt in the origional design is that a user could use several LDB display's (Granted it's not likely). But one could use a minimap style display such as LDBIcon and Bazooka (as i do in SOCD).
The problem happens when you enable the feed, what display should enable?
The Bazooka one, I guess. I'm not real sure how LDBIcon works. It's not an addon in its own right, is it? How do you (if you do) let the user control your minimap icon? Same logic could be applied here, perhaps.
LDBIcon is a Lib in it's own right. The minimap icon is controled by the addon itself as part of it's interaction with LDBIcon. So LDB itself is not being told to hide or show the plugin, but the lib is doing it. LDBIcon is unique in that sense.
yeah, LDBIcon is a display addon in library form that is shipped with your addon. Your addon provides the SV for storing the settings regarding displaying of its data object (whether to show the icon, position, ...) but that has nothing to do with the data object/LDB itself.
Then I would think LDBIcon would not be affected by the proposed property, as it's already being treated differently. (in being controlled by the addon)
I also want to clarify, I didn't mean this simply as a means for users to toggle the feed from within the owner addon, but rather for the (albeit rare) cases where you'd want to "dynamically" toggle it.