Authors CurseForge

@myrroddin
If you want to post or commit to your svn your current code, I'll look at it tonight for ya :)

eh.. iirc, no you can't do this as your describing it.

sorry 4day old post...

ok...


"OnCommRecieved" is a gneric method name that AceComm uses.. however what you want is something like this:

lib:RegisterComm("LGB")

function lib:OnCommReceive(event, prefix, msg, sender)
 ....
end

where "LGB" is what ever your using as your Comm's Prefix to SendAddonMessage()

Quote from myrroddin

Leave the rest of the when sending comms intact?

no..


lib:SendCommMessage("gBankComm", etc)


once AceComm is embedded you treat your lib object as an addon and call the lib's API functions like you would from a standard addon.

Try:

30	AceComm[B]:[/B]Embed(lib) 
31	[B]lib[/B]:RegisterComm("gBankComm", "OnCommReceived")

Move line 52 to line 34 and reEvaluate how :Hash() and :UnHash() work as they are not properly implemented.

A word of advice about functions that send data: You don't want to be sending data out from support functions but from primary ones. IE: if you send a table or hash off to be decompressed or proccessed you should return the results of the proccess to the previous or top level function and let the top level functions communicate out.

No clue what LibDDI is.. but if your talking about LibDropDown-1.0 that was recently came out, then the difference is one is a proper GUI Implementation (AceGUI), think of Blizz's Interface Options. The other is a replacement for DewDrop from the Ace2 days.

DewDrop is just a drop down style interface, LibDropDown implements the AceConfig3 style options table as a drop down instead of how AceGUI implements it as a more refined interface.

yes... other addons that can't seem to hook the ItemRefTooltip properly.. been a problem for quite a while.


Try v6.5-release-8-g73f256a should fix these problems.

However as i did change the Scanner file, you'll need to wait for it to cache all the quest names again, ~40 sec after logging in the first time

ps: please use the ticket tracker, no need to triple post anything, I'm still alive :)

Quote from neocrypter

My question is should i grab Ace and start using the framework right away or as im sure most people would suggest, start by making a few addons from scratch first.

As many suggest, write w/o any framework first. This will give you the most exposure to how addons work in WoW. As for many of the libs around, unless the WoW-API is completely messed up, libs often complicate matters that are rather simple.

Quote from Nevcairiel

AceGUI does not use CallbackHandler.

Pift... close enough :P

Quote from KanadiaN

I was thinking that but when I was browsing the widget's code to try and figure it out on my own I could not see where it was passing self back.. thanks

... That's because of the CBH Stub Magic that AceGUI uses.. but don't worry.
This should work nicely, as i worked with AceGUI alot in one of my addons

     ...
     aGlobal:SetCallback( "OnEnterPressed", function( self, [I]event,[/I] text )
               print("Debug:", text)
          end
     )

edit: So im a bit rusty on the AceGUI widgets, it's been a year or more

aGlobal:SetCallback( "OnTextChanged", function( [B][I]self[/I],[/B] text )
               AddOn:Print( "bug", "test for input = "..text )
          end
     )

Your missing the "self" arg in the callback function. Just about any callbacks that are done wtih Ace3 will have a "self" arg that is the originating object ( the text box in this case )

Quote from Nevcairiel

If i turned them off years ago, and then come back to the settings, wondering how to turn them on again, no its not.

That's what a checkbox outline is for :) tho that's not part of the DefaultUI :(

one has to wonder what your doing when you start futzing around with other addon's sv's

[php]
if (SecureCmdOptionParse("[nogroup]") == "") then
---Not in party
else
--in party
end
[/php]

Might seem overdone, but it works rather well for where i use it :)