This site works best with JavaScript enabled. Please enable JavaScript to get the best experience from this site.
What steps will reproduce the problem?1. Set a non-default border texture and background texture to a2. Log off. Log back on.3. Border and background textures appear to be reset; are still the same in the config. Change a random border/background config value and reset the value back to what it was - you will see the correct border and background appear.
What is the expected output? What do you see instead?A flat border texture and some random background texture. I expect to see the texture I've chosen.
What Grid2 version and language of WoW are you using?## Version: r773## X-ReleaseDate: "$Date: 2015-02-26 02:56:34 +0000 (Thu, 26 Feb 2015) $"
Do you have an error log of what happened?No Bugger entries.
Please provide any additional information below.http://stuff.lhunath.com/Grid2.lua
Working fine here, i dont know which background and border texture you are speaking about, background of the cell / background of the healt-bar ? Enable lua errors, disable other addons and retest the issue, maybe some addon or library is crashing in the log off process and the settings cannot be saved.
Apparently this happens whenever choosing a border provided by another addon.
I suspect that by the time grid2 loads the border texture, the other addon hasn't made the resource available yet? Perhaps grid2 needs to schedule its start-up later or retry loading missing resources instead of defaulting to grid flat?
@lhunath: Go
Grid2 already delays the texture loading, maybe the problem is that the addon providing the texture is not registering the textures early. A timer and ugly code must be added to retry the texture loading , its not grid2 fault if other addon is not registering the textures in the correct event.
Can you tell me which addon is causing this behavior ?
Appears to happen with ArkInventory textures and Raven textures, not Detail! textures.
Reviewed Raven code, and the addon is registering the textures too late, in the wrong event (OnEnable Event). So raven textures cannot be safety used by another addons. You could open a ticket in Raven webpage to suggest moving the textures registering code to the OnInitialize event.
To post a comment, please login or register a new account.