Excellent Addon, it really makes ESO more fun being able to set a lot of styles with all the different options available to me. Instead of taking a half hour each time I feel like a change, I can switch quickly between them. It's no longer a hassle!

I have a feature request - is it possible to set up an auto equip when switching armory slots? The addon seems to have everything else I could ever want, but I'd love to equip a specific outfit for a crafter, and another for my powerhouse, etc.

Cheers!

THank you to both of you Lari and Messajah!!

Don't worry. If this idea is implemented, it would not tie the add-ons together whatsoever. They are both completely standalone still. The integration would simply allow AlphaGear's saved gear sets to apply Quick Fashion profiles whenever you change gear sets, for people who use both addons.

Hello
First thank you for this addon.

Now while i understand totally the need to upgrade and add new functionality, and even for those who would enjoy it with the alpha gear, could you let an option for those who do not want to use alpha gear at all ?

I enjoy simple and easy addons, and i fear that the merge of these two will make your addon a gazillion options and make it very lound to use.

I may be the only one to no like alpha gear at all but i know that if i have to use alpha gear to continue to use your addon, i will not.

In any case, i love your addon and enjoy using it.

Hey, thanks a lot for your positive reply!

I will be writing integration from AlphaGear to Quick Fashion, so that whenever the player loads a set of equipment and ability bars, it also applies the Quick Fashion style that has been saved with that set:

https://www.esoui.com/downloads/info...llsBanking.htm

They already have integration with a basic style manager named AlphaStyle, and all I will need is a reliable way to refer to saved profiles (such as by profile name if that's immutable), and a way to apply the Quick Fashion profile directly in code without interfering with QF's GUI.

If I could describe a perfect API for this purpose, it would be something like:

- QF.GetProfileNames(): Builds a sorted list of the table keys of the current QF.SavedVars.Profiles table. Hopefully those names are immutable. Then they will be a reliable way to store the profile association long term.
- QF.IsProfile(profileName): Checks if profile name exists.
- QF.EquipProfileByName(profileName): Equips profile via its given name (or any other reliable identifier that can be stored in a 3rd party addon) without interfering with the Quick Fashion GUI.

I was also thinking about the possibility that a profile can only exist in either the Account-Wide or Per-Character tables in Quick Fashion, and that the above would break if the user switches Quick Fashion to the other savedvar mode, thereby making QF.SavedVar.Profiles into another table. But that isn't a huge concern since IsProfile() would simply be called to detect that the profile "no longer exists" and therefore the integration wouldn't even attempt to equip it (and I see that the EquipProfileByName function also verifies existence before proceeding).

The APIs above would be enough for an integration.

An unnecessary but larger API improvement to solve the above issue would be if each Quick Fashion profile consisted of two values: type ("account" or "character"), and profile name. And that both tables were always accessible. So that Quick Fashion lists both the global profiles and the character's own profiles in its GUI, and lets the player save new profiles either to the Per-Character or the Account-Wide profiles on a per-profile basis. This would also be a general improvement since people could then choose to make some account profiles and some that only make sense on a specific character. Maybe even with a way to swap the type of a profile inside QF's GUI (moving it to the opposite profiles table at will). Examples of APIs for that would be:

- QF.GetProfileNames(): Returns a table with two keys: "account" and "character", with each containing sorted lists of profile names of each type.
- QF.IsProfile(profileType, profileName): Checks if the named profile exists in the given table (AWSV or character savedvar).
- QF.EquipProfileByName(profileType, profileName): Applies the profile from the given type, if such a profile exists.

But the latter would require some major changes to how Quick Fashion stores and accesses profiles and changes to its GUI, so while I think it would be a good QF feature (being able to have both profile types at the same time, so that people aren't locked into either just Shared or just Per-Character profiles), I would be completely happy with just the first API above. People are unlikely to change savedvar mode often enough that it matters. And if they swap to the other profile-mode, it would be trivial for people to just re-assign things and select the new profile names in any addon that integrates with Quick Fashion. The only reason I brought up the 2nd solution is for consideration, if you like it as a general Quick Fashion feature, since it would be pretty nice to be able to use both profile types at once.

Either solution would be absolutely great! The first one is easiest to implement by far and is almost done already!

Thanks for your help. It will be interesting to hear your thoughts!

I have to say massive massive massive thank you for this addon. It is so beautifully designed and brilliantly easy to use.

If I want to hook into this addon to get a list of all saved fashion profiles and to apply fashion profiles, what would be the best way?

I researched a bit already and found that "QF.SavedVars" is the global way to find the active settings table regardless of whether character or account-wide mode is active.

And that "QF.SavedVars.Profiles" contains the list of profiles that the active character has access to.

What do you suggest next? Does the following idea sound safe?

1. I can get the "Profiles" table keys to let my addon see all profiles contained in Quick Fashion.
2. I am thinking of storing references to profiles by their name. It seems the names cannot be changed in Quick Fashion after a profile has been saved so this seems very reliable.
3. When it's time to apply a profile, I should probably first check in the QF "Profiles" table to see if that key still exists.
4. Lastly, to apply a QF profile by name programmatically from my addon, what code flow should I trigger? I see that the Equip button calls "QF.EquipProfile()" without any parameters, which in turn looks at the drop down profile name selection and then calls "QF.EquipProfileByName(profileName)", which then verifies that the profile exists in the active Profiles table. And then does the work of applying the profile. My question is if it's safe for me to directly call that function without opening Quick Fashion's GUI and without selecting it in the profile dropdown list? The code looks like it operates directly on the "Profiles[profileName]" table and should work, but I want to be sure that things won't break if I call EquipProfileByName directly without manipulating the dropdown list. edit: I noticed that your "/qf (number)" slash command runs "QF.EquipProfileByHotkey" which in turn looks up a profile name, sets the dropdown to it, and THEN calls "EquipProfile()" without parameters, to basically simulate GUI usage. But that is too invasive for me. I'd like to just trigger "QF.EquipProfileByName(profileName)" without modifying Quick Fashion's GUI whatsoever, if that is safe?

Your outfit / fashion addon is by far the best, there's no competition for it at all. So I'd rather integrate with it to trigger its profiles, than trying to replicate its greatness.

The addon panel now opens with the collections menu and this is ideal, but the additional modification panels do not retain their position.

Here is an example of how I feel comfortable placing them.



I have such an opportunity, because. you implemented their displacement.

But when restarting the interface or restarting the game, the addon again "attaches" additional panels to the main window of the addon.



In addition, the Quick Profiles panel does not turn off when you close the collections interface, as the other two panels do.

Is it practical to add another default setting for cities? To allow characters to have a fashion preset they wear while in cities if not overridden by a more specific preset.
Likewise, is it practical to have different presets for different activities? Such as swiming, fishing, crafting or riding? (I'd avoid having a preset for combat, as both costume changes and polymorphs have animations that lock your character up for a second or two.)

Hello. Very interesting addon. Is it possible to implement saving the position of addon windows to a specific interface? In addition, I would like additional windows (Quick Favorites, Quick Profiles) to maintain their position relative to each other. At the moment, if you move one of them to a convenient place for you when you restart the game, they are placed to the default position.