Go to Page... |
Compatibility: | Gold Road (10.0.0) |
Updated: | 06/03/24 01:19 PM |
Created: | 02/14/14 10:28 PM |
Monthly downloads: | 36,668 |
Total downloads: | 5,008,314 |
Favorites: | 2,824 |
MD5: |
IMPORTANT In case you get an error that contains text like this: user:/AddOns/<some other addon>/Libs/LibAddonMenu-2.0 Some other addon you have installed likely contains an old version of LibAddonMenu which is loaded before the most current one. Make sure to search for LibAddonMenu-2.0 folders in your AddOns folder and delete all of them. Afterwards install the latest version of LibAddonMenu-2.0 separately. Check Kyzderp's guide for more detailed instructions |
## DependsOn: LibAddonMenu-2.0
## DependsOn: LibAddonMenu-2.0>=30
local LAM = LibAddonMenu2 local saveData = {} -- TODO this should be a reference to your actual saved variables table local panelName = "MyAddOnSettingsPanel" -- TODO the name will be used to create a global variable, pick something unique or you may overwrite an existing variable! local panelData = { type = "panel", name = "MyAddOn Settings", author = "me", } local panel = LAM:RegisterAddonPanel(panelName, panelData) local optionsData = { { type = "checkbox", name = "My First Checkbox", getFunc = function() return saveData.myValue end, setFunc = function(value) saveData.myValue = value end } } LAM:RegisterOptionControls(panelName, optionsData)
- use the callbacks "LAM-PanelControlsCreated", "LAM-PanelOpened" and "LAM-PanelClosed" instead- updated Brazilian translation (thanks FelipeS11)
- the panel control is returned by RegisterAddonPanel- added "translation", "feedback" and "donation" properties to panel (#88, thanks Baertram)
- all three (and also the "website" property) accept a function or a string- added "disabled" and "disabledLabel" property for submenus (#86, #90, thanks klingo)
- the function receives the value, min and max as arguments and has to return a clamped value- added optional support for LibDebugLogger
- in case it is loaded, it logs the full error when control creation failed- updated LibStub to r5
- when set to true it changes the text color of the button to red and opens a dialog which shows the label and the warning text before running the callback- added new options for sliders and fixed some bugs (#49)
- autoSelect (boolean): when set to true it makes the input field select all text when it gains focus- for other internal code changes take a look at the git history
- inputLocation (string): setting it to "right" will move the input field to the right side of the slider and make it slightly bigger. For aesthetic reasons this should only be used in custom panels and not in the addon menu
- clampInput (boolean): true by default and if set to false it allows the input values of the slider to exceed the min and max value
- NOTE: the menu is now a bit wider than before, if you created custom elements you might need to update them accordingly- added search box to addon list (thanks votan & merlight)
File Name |
Version |
Size |
Uploader |
Date |
2.0 r36 |
49kB |
sirinsidiator |
03/10/24 04:21 PM |
|
2.0 r35 |
49kB |
sirinsidiator |
10/31/23 01:16 PM |
|
2.0 r34 |
48kB |
sirinsidiator |
06/06/22 05:35 AM |
|
2.0 r33 |
48kB |
sirinsidiator |
03/14/22 02:51 PM |
|
2.0 r32 |
48kB |
sirinsidiator |
12/17/20 02:04 PM |
|
2.0 r31 |
49kB |
sirinsidiator |
06/21/20 03:06 PM |
|
2.0 r30 |
48kB |
sirinsidiator |
10/21/19 03:23 AM |
|
2.0 r29 |
48kB |
sirinsidiator |
05/07/19 11:00 AM |
|
2.0 r28 |
47kB |
sirinsidiator |
05/01/19 09:33 AM |
|
2.0 r27 |
47kB |
sirinsidiator |
04/18/19 03:07 PM |
|
2.0 r26 |
45kB |
sirinsidiator |
05/21/18 02:36 AM |
|
2.0 r25 |
45kB |
sirinsidiator |
09/29/17 12:28 PM |
|
2.0 r24 |
45kB |
sirinsidiator |
07/14/17 01:00 PM |
|
2.0 r23 |
42kB |
sirinsidiator |
10/30/16 10:00 AM |
|
2.0 r22 |
39kB |
sirinsidiator |
08/06/16 07:42 AM |
|
2.0 r21 |
38kB |
sirinsidiator |
07/17/16 11:04 AM |
|
2.0 r20 |
41kB |
sirinsidiator |
03/26/16 10:45 AM |
|
2.0 r19 |
37kB |
sirinsidiator |
02/24/16 12:24 PM |
|
2.0 r18 |
36kB |
sirinsidiator |
06/14/15 01:12 PM |
|
2.0 r17 |
30kB |
sirinsidiator |
02/22/15 11:09 AM |
|
2.0 r16 |
27kB |
Seerah |
11/02/14 02:03 PM |
|
2.0 r14 |
26kB |
Seerah |
07/27/14 10:17 PM |
|
2.0 r13 |
26kB |
Seerah |
07/20/14 09:35 PM |
|
2.0 r12 |
26kB |
Seerah |
07/20/14 07:55 PM |
|
2.0 r11 |
26kB |
Seerah |
07/19/14 02:49 PM |
|
2.0 r10 |
25kB |
Seerah |
07/13/14 09:18 PM |
|
2.0 r9 |
25kB |
Seerah |
07/05/14 06:55 PM |
|
2.0 r8 |
25kB |
Seerah |
06/22/14 09:47 PM |
|
2.0 r7 |
25kB |
Seerah |
06/15/14 05:17 PM |
|
2.0 r6 |
25kB |
Seerah |
06/13/14 11:28 PM |
|
2.0 r5 |
25kB |
Seerah |
06/12/14 10:32 PM |
|
2.0 r4 |
25kB |
Seerah |
06/11/14 08:56 PM |
|
2.0 r3 |
25kB |
Seerah |
06/11/14 07:49 PM |
|
2.0 r2 |
24kB |
Seerah |
06/10/14 10:06 PM |
|
1.0 r8 |
6kB |
Seerah |
05/24/14 10:01 PM |
Comment Options |
Drakanwulf |
View Public Profile |
Send a private message to Drakanwulf |
Find More Posts by Drakanwulf |
Add Drakanwulf to Your Buddy List |
02/05/19, 05:36 PM | |||
|
Correct, AddOnVersion > ApiVersion as AddOnVersion can be different with the same api. If the game should check both in combination you need to report this probably to ZOs.
I'd say: The AddOnVersion alone is enough as you'll update it with, or w/o an ApiVersion. For the apiversion: just enable this annoying checkbox and all is OK. Addons will work if they work. AddOnVersion will be checked to load the newest files. If some files are not up 2 date: too bad, but happens. Addons still work.
Last edited by Baertram : 02/06/19 at 03:36 PM.
|
||
|
Baertram |
View Public Profile |
Send a private message to Baertram |
Find More Posts by Baertram |
Add Baertram to Your Buddy List |
02/05/19, 05:28 PM | |
It is neither an inconsistency nor a bug. This is the intended behavior.
I repeat once again: The manifest file too is part of what the AddOnVersion is describing. When you change the manifest, you have to increment the version, otherwise you have two variations of the "code" with the same version number. The APIVersion directive in the manifest is not related to the AddOnVersion, even when both contain "version" in their name. They are completely different things with different purposes and different code checking them for different reasons. Activating the OOD checkbox doesn't do anything more than disabling the check for the APIVersion directive. It is like when you manually replace the APIVersion in the manifest with the current one and follows the same set of rules. There is no "randomized crap-shoot" or anything of the likes happening. It just doesn't seem like you are trying to understand these rules and instead rather post walls of text with incorrect information everywhere. And with that I kindly ask you to stop pestering me and others about it. It is honestly becoming very annoying. |
|
|
sirinsidiator |
View Public Profile |
Send a private message to sirinsidiator |
Find More Posts by sirinsidiator |
Add sirinsidiator to Your Buddy List |
02/05/19, 04:04 PM | ||
Second, LAM-2.0 is not one of my add-ons. Ergo, I cannot change either one of these add-ons in the ESOUI add-ons database because I am not its author. All I can do is to report their inconsistencies. Third, I say it is a bug because I corrected the APIVersion: values in the standalone LAM-2.0 r26 add-on for NA Live but the game still refused to load ANY copy of LAM-2.0, embedded or otherwise, from any other add-on after it had found and marked r26 as bad and OOD. Not even the standalone r26 which had the correct APIVersion: values in its manifest. The refusal to load any LAM-2.0 indicates to me, that the current game code is probably comparing AddOnVersion: values BEFORE it checks for valid APIVersion: values; therefore, the game cannot replace a bad OOD setting with a good setting whenever an add-on's AddOnVersion: values are equal (r26). This bug then prevents a standalone add-on from overriding the APIVersion: values for its embedded and OOD cousins which significantly complicates the add-on loading process. Unless, of course, you choose to turn on the OOD checkbox which turns choosing add-ons by AddOnVersion: value into a randomized crap-shoot. Last, thanks for updating LAM-2.0. It is appreciated despite our different opinions about game bugs. |
||
|
Drakanwulf |
View Public Profile |
Send a private message to Drakanwulf |
Find More Posts by Drakanwulf |
Add Drakanwulf to Your Buddy List |
02/05/19, 06:13 AM | |
What you describe is not a bug in the game. When you have duplicate addons in your folder and change ANYTHING in ANY file that is loaded by the game, you need to increment the AddOnVersion. Otherwise you have two different versions of the addon code with the same version number. The APIVersion is not a tie breaker - it is completely unrelated to the addon version. In your case the game simply cannot tell which one is version it should load, so it picks the one it sees last. If you wanted it to pick the one you adjusted, you'd have to change the AddOnVersion to at least 27.
Aside from that, LAM is not outdated. It works as fine as it did 3 game updates ago and I see no reason to update it without having any real changes in the code, just so you don't have to check a checkbox that everyone is already checking. You are literally the only one to complain about this in the past few years, so it is very obviously not an issue for the playerbase. In WOW the same checkbox existed for more than 10 years and it is also not an issue. They even describe in their wikis and addon guides that you have to make sure that the "Allow outdated addons" checkbox is checked. Maybe something we should do for ESO too. That said, since there is a merge for a new feature pending, I will do an update for Wrathstone which will of course also include the new APIVersion. |
|
|
sirinsidiator |
View Public Profile |
Send a private message to sirinsidiator |
Find More Posts by sirinsidiator |
Add sirinsidiator to Your Buddy List |
02/04/19, 10:40 PM | |
Re: LAM-2.0 r26 Packaging is woefully out-of-date!
Further research has revealed a sneaky game bug having to do with the interaction between the APIVersion: and AddOnVersion: directives. I found it by accident while trying to determine why LAM-2.0 still would not load correctly after I had made the necessary packaging changes to the manifest.txt file to bring its APIVersion: and file loading directives up to standalone and 100025 standards. The changes are:
Code:
## APIVersion: 100025 100026 ## Title: LibAddonMenu-2.0 ## Version: 2.0 r26 ## AddOnVersion: 26 ## Author: Seerah, sirinsidiator, et al. ## Contributors: votan, merlight, Garkin, Randactyl, KuroiLight, silvereyes333, Baertram, kyoma ## Description: A library to aid in the creation of option panels. ## DependsOn: LibStub ## ## This Add-on is not created by, affiliated with or sponsored by ZeniMax Media Inc. or its affiliates. ## The Elder Scrolls® and related logos are registered trademarks or trademarks of ZeniMax Media Inc. in the United States and/or other countries. ## All rights reserved ## ## You can read the full terms at https://account.elderscrollsonline.com/add-on-terms LibAddonMenu-2.0\LibAddonMenu-2.0.lua LibAddonMenu-2.0\controls\panel.lua LibAddonMenu-2.0\controls\submenu.lua LibAddonMenu-2.0\controls\button.lua LibAddonMenu-2.0\controls\checkbox.lua LibAddonMenu-2.0\controls\colorpicker.lua LibAddonMenu-2.0\controls\custom.lua LibAddonMenu-2.0\controls\description.lua LibAddonMenu-2.0\controls\dropdown.lua LibAddonMenu-2.0\controls\editbox.lua LibAddonMenu-2.0\controls\header.lua LibAddonMenu-2.0\controls\slider.lua LibAddonMenu-2.0\controls\texture.lua LibAddonMenu-2.0\controls\iconpicker.lua LibAddonMenu-2.0\controls\divider.lua Combat Metrics Combat Reticle (Baertram's latest modification) LibStub r5 (standalone) LibAddonMenu-2.0 r26 (standalone) If you have your OOD checkbox marked, everything will work, I believe, without modifications but, as soon as you turn the OOD checkbox off, bad things should begin to happen as soon as you execute a /reloadui command. They will continue to happen even after you correct the LibStub and LAM-2.0 manifests; the game will not load LAM-2.0 no matter what you do. I found the reason why by accident when I turned my OOD checkbox on and everything loaded just fine but returned to dependency failures as soon as I turned the OOD checkbox off. And this is why... There is an OOD LAM-2.0 folder embedded within the Combat Metrics folder that is referenced as a dependency by its manifest file. The game will not load this LAM-2.0 file because its APIVersion: is 100023; therefore, it is a bad, OOD addon but, and here is the kicker in this scenario, the AddOnVersion: in the manifest for this file says that its value is 26! Bingo! Same, latest, AddOnVersion: value for both the bad and good files. It appears that the game will not load any successive LAM-20 files with the same AddOnVersion: value because it has already marked the first one as bad and OOD; not even when the files have a corrected APIVersion: value (100025) in their manifests! The wiki says that the game randomly picks one of an add-on set whenever multiple copies (AddOnVersion: value) exist. I expect this is what happened here but I am guessing. You can prove this for yourselves by deleting the LAM-2.0 folder from the Combat Metrics folder and by adding "LibAddonMenu-2.0" to its DependsOn: directive. Turn the OOD checkbox off and on between /reloadui commands to watch everything work exactly as it should. My thanks to Baertram for his asking me to fix the problem rather than whinging about it. Baertram, I would if I could but I don't work for ZOS and I am not the author of LAM-2.0. However, I expect there have been, are, or will be similar occurrences whenever an OOD add-on contains the same AddOnVersion: values in its manifest. |
|
|
Drakanwulf |
View Public Profile |
Send a private message to Drakanwulf |
Find More Posts by Drakanwulf |
Add Drakanwulf to Your Buddy List |
02/04/19, 03:51 PM | |
LAM-2.0 r26 Packaging is woefully out-of-date!
When attempting to test Baertram's upgrades to Combat Reticle, I found that the upgrade would not load because there was no LAM 2.0 for it to use, so I downloaded and installed the latest standalone LibStub and LAM 2.0 libraries from ESOUI.
I should not have downloaded LAM 2.0 because it has not been updated since 100023; it has a naked, out-of-date (r4) LibStub embedded within it; and it has no DependsOn: directive to instruct the game to find and use the latest LibStub. If you would open the latest LAM folder in ESOUI and check the manifest.txt file, you can verify that my statements are accurate. Then, if you would check the rest of the LAM folder's contents. I believe you will find that the embedded, naked, LibStub.lua file is an out-of-date, r4, version, rather than the current, stand alone, r5, version that exists in ESOUI. I would appreciate it very much if the author or a designated person would upgrade the LAM 2.0 r26 packaging to be compatible with standalone requirements and APIs 100025 and 100026. If I fix LAM for myself, my fixes do not get back to ESOUI because I am not the author and because I am not the author, my changes could work for me but not for everyone else who plays the game. Thank you for your consideration,
Last edited by Drakanwulf : 02/04/19 at 09:44 PM.
|
|
|
Drakanwulf |
View Public Profile |
Send a private message to Drakanwulf |
Find More Posts by Drakanwulf |
Add Drakanwulf to Your Buddy List |
12/28/18, 10:24 PM | |
Forum posts: 0
File comments: 40
Uploads: 0
|
Update Status?
FCO Item Saver is apparently still dependent on this library, so I'd like to know if you or your group project folks are going to be updating this for Murkmire, and/or future patches?
|
|
MoonDancer |
View Public Profile |
Send a private message to MoonDancer |
Find More Posts by MoonDancer |
Add MoonDancer to Your Buddy List |
10/05/18, 06:08 PM | ||
Force panel widgets to update...
EDIT: The problem ended up being unrelated. Setting a local variable 'myPanel' to the return value from RegisterAddonPanel and then calling CALLBACK_MANAGER:FireCallbacks("LAM-RefreshPanel", myPanel) at the point in my code I want to refresh does in fact appear to be refreshing all widgets.
Last edited by Phinix : 10/06/18 at 03:59 AM.
|
||
|
Phinix |
View Public Profile |
Send a private message to Phinix |
Visit Phinix's homepage! |
Find More Posts by Phinix |
Add Phinix to Your Buddy List |
09/15/18, 04:35 PM | |
Forum posts: 0
File comments: 16
Uploads: 0
|
You need to change the tool bar and space out some of the icons.
|
|
Hibiki54 |
View Public Profile |
Send a private message to Hibiki54 |
Visit Hibiki54's homepage! |
Find More Posts by Hibiki54 |
Add Hibiki54 to Your Buddy List |
09/05/18, 05:33 PM | ||
Re: Addon Marked as Out-of-Date
Probably(!) you have some other addon with LibAddonMenu in the package, that has other (bigger) Version, so it overwrites the "right" one.
|
||
|
SilverWF |
View Public Profile |
Send a private message to SilverWF |
Visit SilverWF's homepage! |
Find More Posts by SilverWF |
Add SilverWF to Your Buddy List |
08/15/18, 03:26 PM | |
Forum posts: 1
File comments: 82
Uploads: 0
|
Addon Marked as Out-of-Date
No matter what I do, this addon is marked as out-of-date by ESO, which would of course be potentially problematic if the "load out-of-date addons" option is unchecked. Anyone have any idea what I'm doing wrong? Here's the header of the manifest:
Code:
## APIVersion: 100024 ## Title: LibAddonMenu-2.0 ## Version: 2.0 r26 ## Author: Seerah, sirinsidiator, et al. ## Contributors: votan, merlight, Garkin, Randactyl, KuroiLight, silvereyes333, Baertram, kyoma ## Description: A library to aid in the creation of option panels. Edit: Okay, this is really weird. I moved every addon other than LAM out of the addons folder, then deleted every file in the LAM folder other than the manifest. Then I stripped the manifest down to just two lines: Code:
## APIVersion: 100024 ## Title: LibAddonMenu-2.0
Last edited by F-Lambda : 08/15/18 at 05:48 PM.
|
|
F-Lambda |
View Public Profile |
Send a private message to F-Lambda |
Visit F-Lambda's homepage! |
Find More Posts by F-Lambda |
Add F-Lambda to Your Buddy List |
07/24/18, 01:53 PM | ||
Re: colorpicker in gamepad mode
Code:
if IsInGamepadPreferredMode() then COLOR_PICKER_GAMEPAD:Show(ColorPickerCallback, r, g, b, a, LAM.util.GetStringFromValue(colorpickerData.name)) else COLOR_PICKER:Show(ColorPickerCallback, r, g, b, a, LAM.util.GetStringFromValue(colorpickerData.name)) end Gandalf
Last edited by Gandalf : 07/24/18 at 03:53 PM.
|
||
|
Gandalf |
View Public Profile |
Send a private message to Gandalf |
Visit Gandalf's homepage! |
Find More Posts by Gandalf |
Add Gandalf to Your Buddy List |
07/24/18, 04:05 AM | |
colorpicker in gamepad mode
When enabling gamepad mode using colorpicker won't work:
Code:
EsoUI/Libraries/ZO_Dialog/Gamepad/ZO_GenericDialog_Gamepad.lua:280: attempt to index a nil value stack traceback: EsoUI/Libraries/ZO_Dialog/Gamepad/ZO_GenericDialog_Gamepad.lua:280: in function 'ZO_GenericGamepadDialog_SetupDirectionalInput' EsoUI/Libraries/ZO_Dialog/Gamepad/ZO_GenericDialog_Gamepad.lua:521: in function 'ZO_GenericGamepadDialog_Show' EsoUI/Libraries/ZO_Dialog/ZO_Dialog.lua:739: in function 'ZO_Dialogs_ShowDialog' (tail call): ? EsoUI/Libraries/ZO_Dialog/ZO_Dialog.lua:328: in function 'ZO_Dialogs_ShowGamepadDialog' EsoUI/Libraries/ZO_Dialog/ZO_Dialog.lua:265: in function 'ZO_Dialogs_ShowPlatformDialog' EsoUI/Common/ZO_ColorPicker/ZO_ColorPicker_Shared.lua:136: in function 'ZO_ColorPicker_Shared:Show' user:/AddOns/LuiExtended/libs/LibAddonMenu-2.0/controls/colorpicker.lua:82: in function '(anonymous)' |
|
|
Gandalf |
View Public Profile |
Send a private message to Gandalf |
Visit Gandalf's homepage! |
Find More Posts by Gandalf |
Add Gandalf to Your Buddy List |
07/20/18, 11:23 AM | |
If i read right, the add-on could use some love to create dynamic menus?
|
|
|
Ek1 |
View Public Profile |
Send a private message to Ek1 |
Send email to Ek1 |
Visit Ek1's homepage! |
Find More Posts by Ek1 |
Add Ek1 to Your Buddy List |