#763 Titan Panel forgets about disabled plugins

[Anonymous]

Originally created by: karl_...@hotmail.com

What version of Titan Panel are you using and on what operating system?
Titan Panel 5.0.11.40300, Windows 7 32 bit

What steps will reproduce the problem?
1. Enable a plugin to be shown on a bar
2. Log out, disable that plugin only
3. Log back in, and out again
4. Re-enable that plugin, and log back in

What is the expected output? What do you see instead?
I expect the plugin to reappear on the titan panel bar, but it does not.

Please provide any additional information below that you feel is relevant.
I believe it also effects plugins with a delayed load (ie. using AddonLoader), because the plugin isn't loaded when Titan populates the bars.

[Anonymous]

Originally posted by: urn...@gmail.com

I respectfully disagree that Titan should remember where disabled plugins were displayed.
5.0.11 made changes to remove issues some users were seeing because Titan remembered some plugins that were no longer enabled.
On entering the world Titan will display the last saved display list - if the plugins are registered.

I have not played with AddonLoader. If it 'prevents' Titan plugins from being registered when the player enters the world then I can understand this would be frustrating. If we get enough requests we'll see what we can work out.

[Anonymous]

Originally posted by: oscarucb

AddonLoader is a widely-used addon that loads addons at appropriate times, often very long after PLAYER_ENTERING_WORLD. Some addons roll their own dynamic loading using Blizzard's built-in facilities for this. Many of those load-late addons include LDB launchers or data sources.

I respectfully submit that any LDB broker (such as TitanPanel) that ignores those late-registered LDB brokers is fundamentally broken. These addons are not "disabled" they are merely loaded on demand when the user needs them (eg on opening the AH, talking to a vendor, joining a raid, entering a certain zone, etc).

IMHO TitanPanel should remember the settings for ALL plugins (possibly keeping the settings hidden until they load to avoid confusion), and apply the settings when the plugin registers, regardless of when that happens.

[Anonymous]

Originally posted by: urn...@gmail.com

To be clear, late loading LDB addons should be registered with Titan and available for display.
Late loading Titan plugins may register with Titan at PLAYER_ENTERING_WORLD depending on how they are coded. These plugins do need more testing though. If someone points me to a late loading Titan plugin then I'll see what, if anything, is broken.

That leaves the 'memory' of displayed addons.
I hear your point about delayed addons. I'll have to research a sampling of delayed loading addons to test.

Status: Pending

[Anonymous]

Originally posted by: urn...@gmail.com

Issue 765 has been merged into this issue.

[Anonymous]

Originally posted by: urn...@gmail.com

The change was reverted and will be released as soon as practical.
If you want the functionality before then open up TitanVariables.lua. Comment out line 526.
--            table.insert(to_remove, id)
Then Titan will remember (not clean up actually) the locations of the displayed plugins. Please try the above change and let me know.

kernighan - this is why your BankItems was not displayed.

Status: Testing

[Anonymous]

Originally posted by: urn...@gmail.com

(No comment was entered for this change.)

Status: Resolved