you could also use a lib like libsimpleoptions that will allow you to add your addon to the blizzard ui settings menu
In my case, that is not what I want to do. The feature is a dropdown menu of the available factions to allow quickly selecting one to look at or quickly checking what level you're at with the faction.
You don't have to use the EasyMenu wrapper. You can also use the UIDropdown API directly. Depending on what you want to achieve, you still have to jump through some hoops, but it is far more versatile than EasyMenu makes it appear to be.
Is there still no Ace3-ified library for dropdowns? Yeah, sure, AceConfig is nice for overall setup, but there are places where it'd be really nice to offer a quick menu for little tweaks.
AceConfig is not AceGUI. The 2 are very different, however, related. AceConfig is the Ace3 Options Table Spec implemented with AceGUI. AceGUI is the base, where as AceConfig uses that base to implement an options spec.
Now I've used AceGUI directly, it's quite nice and quite functional... a bitch to deal with, but performs EXACTLY as I wanted it for where I use it. Imp sure you could hack up a set of frames to anchor a AceGUI-Dropdown to and use AceGUI directly as a dropdown... but you might as well at that point just use Easymenu or the Blizzard Spec directly.
However as I write that, you could, using AceGUI, create a standalone group frame and add it's dropdown too it, then anchor that group frame to what ever. Then rig it to when you mouse over that frame it would appear OR set it up to automatically open the drop down on right click .... but id rather see narg make a proper AceGUI / AceConfigDropDown for us instead of hacking it up to do things it's not supposed to
AceConfig is not AceGUI. The 2 are very different, however, related. AceConfig is the Ace3 Options Table Spec implemented with AceGUI. AceGUI is the base, where as AceConfig uses that base to implement an options spec.
Now I've used AceGUI directly, it's quite nice and quite functional... a bitch to deal with, but performs EXACTLY as I wanted it for where I use it. Imp sure you could hack up a set of frames to anchor a AceGUI-Dropdown to and use AceGUI directly as a dropdown... but you might as well at that point just use Easymenu or the Blizzard Spec directly.
However as I write that, you could, using AceGUI, create a standalone group frame and add it's dropdown too it, then anchor that group frame to what ever. Then rig it to when you mouse over that frame it would appear OR set it up to automatically open the drop down on right click .... but id rather see narg make a proper AceGUI / AceConfigDropDown for us instead of hacking it up to do things it's not supposed to
:D
Thanks for the rundown. Now if only there was some kind of central documentation for Ace3 that had this sort of detail... =D
I guess what I'm hoping for is what you describe, an actual AceConfigDropDown, using the same AceOptions table spec that every other configure-ish thing uses in Ace3. Seems like a glaring omission. :)
Thanks for the rundown. Now if only there was some kind of central documentation for Ace3 that had this sort of detail... =D
I guess what I'm hoping for is what you describe, an actual AceConfigDropDown, using the same AceOptions table spec that every other configure-ish thing uses in Ace3. Seems like a glaring omission. :)
It was on purpose - thats why it seems glaring. Dewdrop style menus were very out of fashion.
Seems like "framework agnostic" is no longer in vogue though.
It was on purpose - thats why it seems glaring. Dewdrop style menus were very out of fashion.
Well, call me old fashioned, but I sure don't want to have to pull up the full-blown screen-covering feature-complete addon configuration window just to change one setting on one frame of my addon.
Using dewdrop style menus exclusively, sure, kind of lame, out of fashion, we have moved on. But they have a purpose and a place where they excel -- in my case, offering smaller-scope targeted configuration for specific visual components, rather than having to wade through settings for the entire addon in the middle of a fight (and don't tell me people don't configure addons in combat, it does happen).
If some people don't want to use them, fine, they can ignore that library -- the whole idea of Ace3 was better compartmentalization, right? But the question of dewdrop-ish menus in Ace3 seems to have come up more than once now, so I don't think I'm the only one who would use it.
AceConfig is not AceGUI. The 2 are very different, however, related. AceConfig is the Ace3 Options Table Spec implemented with AceGUI. AceGUI is the base, where as AceConfig uses that base to implement an options spec.
Now I've used AceGUI directly, it's quite nice and quite functional... a bitch to deal with, but performs EXACTLY as I wanted it for where I use it. Imp sure you could hack up a set of frames to anchor a AceGUI-Dropdown to and use AceGUI directly as a dropdown... but you might as well at that point just use Easymenu or the Blizzard Spec directly.
However as I write that, you could, using AceGUI, create a standalone group frame and add it's dropdown too it, then anchor that group frame to what ever. Then rig it to when you mouse over that frame it would appear OR set it up to automatically open the drop down on right click .... but id rather see narg make a proper AceGUI / AceConfigDropDown for us instead of hacking it up to do things it's not supposed to
:D
It's far easier than that... Just use the 'Dropdown-Pullout' widget, it's :Open method takes the same parameters as frame:SetPoint and it provides just the dropdown, without any fancy stuff like a button to open it.
The Dropdown-Pullout was designed to be a possible base for AceConfigDropdown, so it should'nt be too hard to use it for a custom dropdown.
But all in all an AceConfigDropdown would be nice sometimes...
If someone sees a quicker way to do it let me know, now to use Dewdrop along AceConfig without conflicts I use http://lua-users.org/wiki/CopyTable to clone the Ace3 formatted option table, then I apply changes (almost only "input" types to change in "text" and the AceDBOptions to remove) to that cloned table and I can call it safely in Dewdrop, I find this method handy because I dont have to manage 2 tables infile, one for dew and one for AceConfig3 but there is maybe quicker ways to do it bcuz I like weed and sometime passing over things that are evidents lolz
I tire of the long-standing debate over the whole thing. The idea of a "library" is to make things more simple. Can we use other methods? Yes. But DD is easier to use and has a shitton more features than the alternatives.
Now, not to be an ass, but, if you don't like the idea of a DD-3.0 library, why bother posting? If you wouldn't use it, then your opinion is kind of irrelevant, is it not?
All we need to do is drop AceLibrary for LibStub, make a few tweaks and tag it 3.0. It works fine. Great, in fact. And despite what people say, DD is NOT a "large" library. As far as that goes, if someone with a lot more experience doesn't want to fool with it, I will.
I don't personally see the point in re-working DD to use Libstub instead of AceLibrary, in terms of gain. Do people get really annoyed for having to embed AceLibrary ? That being said, I do agree that DD is still very much usable and configurable, the debate is simply derived from the fact that people may not want to use certain features, so they consider them as "bloat". Others don't really mind. Perhaps splitting it, in a similar fashion/logic to what LibQTip did, might satisfy both sides.
that because ppl embed Drewdrop-2.0 folder only but they should rather embed DrewdropLib folder which alredy embed AceLibrary. I don't see an urge to replace AceLibrary to LibStub if its already embedding it, that would have been much boring if DD would have required full Ace2 for example
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumIn my case, that is not what I want to do. The feature is a dropdown menu of the available factions to allow quickly selecting one to look at or quickly checking what level you're at with the faction.
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumAce3 has dropdown methods?
I was only aware of full-scale GUI methods in AceConfigDialog.
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumAceConfig is not AceGUI. The 2 are very different, however, related. AceConfig is the Ace3 Options Table Spec implemented with AceGUI. AceGUI is the base, where as AceConfig uses that base to implement an options spec.
Now I've used AceGUI directly, it's quite nice and quite functional... a bitch to deal with, but performs EXACTLY as I wanted it for where I use it. Imp sure you could hack up a set of frames to anchor a AceGUI-Dropdown to and use AceGUI directly as a dropdown... but you might as well at that point just use Easymenu or the Blizzard Spec directly.
However as I write that, you could, using AceGUI, create a standalone group frame and add it's dropdown too it, then anchor that group frame to what ever. Then rig it to when you mouse over that frame it would appear OR set it up to automatically open the drop down on right click .... but id rather see narg make a proper AceGUI / AceConfigDropDown for us instead of hacking it up to do things it's not supposed to
:D
Thanks for the rundown. Now if only there was some kind of central documentation for Ace3 that had this sort of detail... =D
I guess what I'm hoping for is what you describe, an actual AceConfigDropDown, using the same AceOptions table spec that every other configure-ish thing uses in Ace3. Seems like a glaring omission. :)
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumIt was on purpose - thats why it seems glaring. Dewdrop style menus were very out of fashion.
Seems like "framework agnostic" is no longer in vogue though.
Well, call me old fashioned, but I sure don't want to have to pull up the full-blown screen-covering feature-complete addon configuration window just to change one setting on one frame of my addon.
Using dewdrop style menus exclusively, sure, kind of lame, out of fashion, we have moved on. But they have a purpose and a place where they excel -- in my case, offering smaller-scope targeted configuration for specific visual components, rather than having to wade through settings for the entire addon in the middle of a fight (and don't tell me people don't configure addons in combat, it does happen).
If some people don't want to use them, fine, they can ignore that library -- the whole idea of Ace3 was better compartmentalization, right? But the question of dewdrop-ish menus in Ace3 seems to have come up more than once now, so I don't think I'm the only one who would use it.
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumIt's far easier than that... Just use the 'Dropdown-Pullout' widget, it's :Open method takes the same parameters as frame:SetPoint and it provides just the dropdown, without any fancy stuff like a button to open it.
The Dropdown-Pullout was designed to be a possible base for AceConfigDropdown, so it should'nt be too hard to use it for a custom dropdown.
But all in all an AceConfigDropdown would be nice sometimes...
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumNow, not to be an ass, but, if you don't like the idea of a DD-3.0 library, why bother posting? If you wouldn't use it, then your opinion is kind of irrelevant, is it not?
All we need to do is drop AceLibrary for LibStub, make a few tweaks and tag it 3.0. It works fine. Great, in fact. And despite what people say, DD is NOT a "large" library. As far as that goes, if someone with a lot more experience doesn't want to fool with it, I will.
Elaborate please. Suggesting what would be acceptable would be a constructive contribution to the discussion.
You're asking Arrowmaster for a constructive contribution to the discussion?