"Custom Triggers" tab - collapsible categories (suggestion)

HonigBall

Hey!

I am using ACT for Everquest 2 for years now and thus have accumulated a mass of different triggers. Sometimes, when searching for certain triggers, it takes quite a while scrolling through all the categories until I find the trigger I need to share.

Whenever I tried to collapse some of the older categories to reduce the size of the page, it seems ACT does not remember the "state" (collapsed / not collapsed) after restarting, so I would need to collapse them after every start.

Most of the triggers are not needed anymore, but I do not want to delete them, just in case I revisit older zones. Would it be feasible to add the possibility of saving the current state of (or maybe even hiding) categories to ease scrolling through the triggers?

Thanks a lot!

EQAditu

I might as well comment now that I've given it a moment of thought.

It's not super easy because the existence of categories are not technically saved in the config files.  Each spell/trigger is its own config line and each one mentions a category.  

<CustomTriggers>
    <Trigger Active="True" Regex="aa" SoundData="" SoundType="0" CategoryRestrict="False" Category=" General" Timer="False" TimerName="" Tabbed="False" />
    <Trigger Active="True" Regex="bb" SoundData="" SoundType="0" CategoryRestrict="False" Category=" General" Timer="False" TimerName="" Tabbed="False" />
    <Trigger Active="True" Regex="cc" SoundData="" SoundType="0" CategoryRestrict="False" Category=" General" Timer="False" TimerName="" Tabbed="False" />
    <Trigger Active="True" Regex="aa" SoundData="" SoundType="0" CategoryRestrict="False" Category="123" Timer="False" TimerName="" Tabbed="False" />
    <Trigger Active="True" Regex="bb" SoundData="" SoundType="0" CategoryRestrict="False" Category="123" Timer="False" TimerName="" Tabbed="False" />
</CustomTriggers>

But the categories are not mentioned on their own in the config.  The categories only end up existing because a spell/trigger mentions it.  There's not a great place to store UI treenode expansion.

I would have to come up with a custom solution on where to store this data.