Hopefully I didn't break it...
local fragment = ZO_HUDFadeSceneFragment:New(yourTopLevelControlName, nil, 0) --You can also just use ZO_SimpleSceneFragment instead of ZO_HUDFadeSceneFragment HUD_SCENE:AddFragment(fragment) HUD_UI_SCENE:AddFragment(fragment)
I'd guess the combat log is a TopLevelControl as you said so it got a control that can be added to a "fragment".
A fregment is reusable code (e.g. the player inventory list control which will be reused at normal player inv, bank deposit, guildbank deposit, mail, trade, sell at guild store e.g.) used in game scenes. A scene defines something like the shown panels (guild bank, bank, trading house, mail, ...).
You can craete your own custom fragment and assign it to the GUI and HUD_GUI scenes as changing the scenes will hide/show the fragments automatically. This way you can e.g. make a custom reminder icon texture control show and hide with the menus.
Here is an example at the ESOUI Wiki:
https://wiki.esoui.com/How_to_hide_controls_as_menu_openslocal fragment = ZO_HUDFadeSceneFragment:New(yourTopLevelControlName, nil, 0) --You can also just use ZO_SimpleSceneFragment instead of ZO_HUDFadeSceneFragment HUD_SCENE:AddFragment(fragment) HUD_UI_SCENE:AddFragment(fragment)
yourTopLevelControlName needs to be the global control (TLC) which holds this addon's combat log then.
But you would also need to remove older other code that handles the show/hide currently so I guess it won't be an easy fix.
Search for <yourTopLevelControlName>:SetHidden(true) or false to find where it might get hidden/shown
I had used FTC in the past but disabled it years ago as it got slow and made by game lag.
For now I'm only using Azurah to move vanilla UI controls like the attribute bars and only a few UI related addons (Perfect Pixel e.g.).
Less addons = more speed.
I dislike those total UI addons like AUI or Hoft's Bandit stuff (beside the fact that it includes many things, likeFTC, I'd never use they also often run events and code where not needed, even if disabled -> Error prone/ressource hungry/performance loss).
Here is the GitHub link to the addon repository
if you are used to GitHub: Fork it and patch it in your fork with your changed code, then send a pull request so Rhyono get's your version code and is able to officially update it at www.esoui.com from GitHub.
This way all benefit.