You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
User-defined Icons that are defined for a folder in the tree without a matching Folder tab are not retrieved / displayed anymore - at least in large profiles converted from older versions of Thunderbird. We may also see many warnings of exceptions caught in folder tree, similar to this:
QuickFolders.FolderTree.getCellPropertiesQuickFolders.FolderTree.getCellProperties(14,[object TreeColumn])
returning unchanged props for folder [nstmp] :
Component returned failure code: 0x80550007 [nsIMsgFolder.getStringProperty]
which may be a side effect of invalid icons (to be investigated). With many messages like this, performance may be impacted adversely.
It looks like we will need to store custom icon settings externally (so far I managed to store them in the folders themselves by monkey-patching the function gFolderTreeView.getCellProperties - if we store icon definitions in QuickFolders extension storage (which gets stored in prefs.js) it will be necessary to redefine all icons for (non-tab) folders that are not declared via a dedicated QuickFolders tab.
The text was updated successfully, but these errors were encountered:
In order to make testing a little easier and improve performance + signal-to-noise ratio in the error log, here is a version of QuickFolders that omits the message (the error is still thrown, but it happens "quietly":
I removed an unnecessary call to the function repairTreeIcons() on startup to save on processing time in Thunderbird 102 - this will also have additional effects for issue #283.
User-defined Icons that are defined for a folder in the tree without a matching Folder tab are not retrieved / displayed anymore - at least in large profiles converted from older versions of Thunderbird. We may also see many warnings of exceptions caught in folder tree, similar to this:
which may be a side effect of invalid icons (to be investigated). With many messages like this, performance may be impacted adversely.
It looks like we will need to store custom icon settings externally (so far I managed to store them in the folders themselves by monkey-patching the function
gFolderTreeView.getCellProperties
- if we store icon definitions in QuickFolders extension storage (which gets stored in prefs.js) it will be necessary to redefine all icons for (non-tab) folders that are not declared via a dedicated QuickFolders tab.The text was updated successfully, but these errors were encountered: