LibAddonMenu-2.0 r31 beta
This release removes the embedded LibStub which may cause an error in case an addon relied on LAM as a source for LibStub and LibStub isn't installed separately by the user. So I decided to post it here first in order to give authors and users a chance to do some testing before I upload it for everyone.
- fixed iconpicker showing an empty tooltip when no choicesTooltips are set (#111, thanks Scootworks)
- fixed slider mouse wheel interactions (#115)
- fixed translated texts not showing in the official Russian localization (#118, thanks andy.s)
- improved dropdown choice tooltip code compatibility (#115)
- added "helpUrl" property for many control types (#109, thanks Baertram)
- added "textType" and "maxChars" properties for editbox (#110, thanks Scootworks)
- added "readOnly" property for slider (#112, thanks Scootworks)
- removed embedded copy of LibStub (#116)
- updated Japanese translation (#113, thanks Calamath)
- updated for Greymoor
so far no issues. also tested #112 and #111 specifically
Thanks both of you. If nobody else experiences any problems, I plan to release it tomorrow.
Had a look at #115, works flawless now.
Was not aware that one can assign a namespace to SetHandler :o
Really like this solution.
The new version is now live. Thanks everyone who tested it.
Technically this is not an issue with LibAddonMenu-2.0, but with the removal of the embedded LibStub which broke Wykkyd's Toolbar, DarkUI, PointsOfColor, and ConspicuousQuestMarkers. Nothing to do on this end I dont think. Those authors just need to update their addons to remove LibStub properly.
But the removal of LibStub in total was communicated since Summerset patch, >2 years ago now.
These addons just need to:
1. switch from these kind of source lines:
If the librray does not exist with it's own txt file it can be kept inside there.
But if it's a real library, meant to be reused in several addons, it should be release WITH a txt file, or the code should be maybe not in a library but directly in the addon's lua files.
3. Inside the addon's txt files the hardcoded lines to the libraries, which were removed from the subfolders, need to be removed.
## DependsOn: <libraryName1> <libraryName2>>=<libraryVersion>
## OptionalDependsOn: <libraryName1> <libraryName2>>=<libraryVersion>
to define if the addon will not load without the librray (and version) installed (## DependsOn)
or if the addon will load without the librray (and version) installed, but it optionally will load the libs first (if found!).
<libraryName1> = the name of the library's txt file or foldername
if >= is specified after the libraryname a "version check" will be done. Only libs with this, or a higher version, will be loaded!
<libraryVersion> = the integer number from the library's txt file's tag ## AddOnVersion: <integerNumber>
So e.g. use
5. You may also download the complete library, including their txt file, and put them extracted to the subfolder "libs" of your addon. This will make the addon manager find the txt files in there and check if your version is the newest one to load. But including them without txt files or even ALWAYS load them hardcoded from your addon's txt file will most probably create errors and problems. So freain from using this way of library loading where NOT NEEDED (e.g. lib does not provide a txt file [yet]).
Additional info for lua addon developers, regarding included libraries:
Additonal library/dependency information can be found here:
|All times are GMT -6. The time now is 09:33 PM.|
vBulletin © 2020, Jelsoft Enterprises Ltd
© 2014 - 2020 MMOUI