WowAce

thanks.  that's useful info.  max's would be nice to see as well, but i can see that the processing happens when the inventory has been updated (three suspect functions here) and when the skill ranks change (2 suspect functions).

curious how things respond if you clear out the numbers and force either of these messages (click the name).  is the processing smart enough to not do anything...?

oops.  forgot i added a new file.  sigh.

make sure to exit the client when updating so the file will be seen.

the latest revision has a frame to assist in debugging.  gw uses messages to trigger a lot of the internal updates.  i've added a simple frame to allow monitoring the messages and their execution times to help me figure out some places where gw might be bogging down.  if you are experiencing lags, you can type "/gw debug" to bring up the message dispatch frame.  there are maybe a dozen or so messages and probably only a few of them really get used with any frequency.

they are named for what process fired them off or what status has changed, so it might not be totally clear what each message actually relates to in terms of processing.  for example, the inventoryScanComplete message actually doesn't include the time it takes to scan the inventory.  instead it's the time it takes to update the queue (mostly).

anyway, you can click on a message to force it to fire to see how gw reacts (to help identify if a message needs to be sent in a particular sequence... like maybe there's a case where something's not updating properly and you find that forcing a particular message fixes the problem).  if you click on the times/counts, they'll reset themselves.  they should be mostly self explanatory.  the "hooks" column indicates the number of functions that were listening for that message the last time it executed.  the max column is the maximum time it took to process that a particular message.

the times don't exclude submessages (yet) so if one message triggers a function that fires off another message, then both messages are assessed the time of that submessage.  i'll change this at some point to get a better accounting for time spent.

hopefully this tool will be useful for people experiencing slowdowns as a means to understand where those slowdowns are coming from.

sprocket, you can change the queue layout to "flat" and it will collapse like recipes/reagents into single entries.  adjusting reagent sources at this level affects all entries.

ignoring particular inventories is going to be a big step and it's something i plan on doing soon.  i want to approach the problem is a very modular way which requires some reworking of the basic inventory code (which it needs anyway because there's something wrong at the moment).  once i rework it to be modular, it will be possible to easily adjust what gw tracks and how it presents that information.

i'm not entirely sure i follow your comment about the grouping of ah purchases.  i do agree that the ah scanning can be overwhelming with information that is hard to understand, so i'm working a means to help make it simpler.  the latest version lists all reagents you might be interested in from your queued items.  this list is only the items it can't find in your bags/on your alts.  it's an easy way to comparison shop, but unfortunately there's no way to know what is really comparing to what.  i want to organize this better so that it's more clear what your options are.  i have some ideas on how to get this working better.

you can always ignore suggestions with gw.  the primary design goal with gw is the idea of a dynamic queue that reacts to changing inventory.  if it says buy peacebloom and you say f it and buy silverleaf, gw will see you have silverleaf and automatically use it instead.  in fact, most of the shopping list buttons aren't actually tied to a particular use.  that is, if you click an item in the bank retrieval list while you're at a vendor, gw will try to buy that item from the vendor.  i think only the auction items are explicitly linked to firing off auction scans, but i might be wrong there.

glad you like it and thanks for the feedback.

asesine, you do have gw running on the alts, right?  i changed the way i'm adding up alt inventory to hopefully be somewhat more efficient, but i think it's likely broken as a few people have mentioned incorrect counts.  i plan on working on this code again today.

esran, the auction tab ties into the gw reagent price scanner to help you determine what reagents are available at the auction house (and to help identify a good price for those items).  queue up your items, visit the auction house, hit scan (from the queue frame or from the auction tab) and it will scan for every reagent that might be useful to your current queued recipes to compare different methods to craft what you want.  you can use the auction tab to quickly buy the reagents you need and compare prices between different pathways to your goal.

sarah, the problem with 106/107 is that i'm trying to optimize the dynamic queue computations and i think i've unplugged something related to the update cycle.  basically, it used to update the queue on every bag update event (event in the general sense, not the actual api event).  so when you'd craft an item, it'd update.  when you'd loot something, it'd update.  i've tried to optimize this, but now it's missing times where it should update.  i'll see where i'm goofing up.

somebody else mentioned an inability to change recipe sources.  i wonder if you're experiencing the same problem.  not sure what's changed in that regard lately... i've been concentrating on different aspect of the code recently because after taking a few days away from the project, the intricacies of exactly what i was doing were a bit vague.  especially since it's been so fluid.  maybe coming at it fresh will be a good thing.

i agree that having a "do not use this" option would be valuable.  the auction tab contains the full list of all reagents being considered for purchase.  that would be a great place to add a temporary flag to avoid that item.

i feel like the auction tab needs some way to help you identify why those reagents were added and which ones are related to each other.  maybe it the auction tab reagent list should break down by manual queue entry.  so instead of every reagent you need, it would list your queued glyphs and then you could open those glyphs to see all the reagents they need (possibly even adding a count column).  i think that would help organize things a bit better.  right now, it seems like information overload.  ideally, i want the user to be able to comparison shop for the correct items as even if gw was good at pricing, it's still worthwhile to give the user the ability to verify or over-ride for whatever reason.

i haven't really done much to the pricing scheme.  i think i'm favoring the manual approach first which will help me debug the automatic approach later.  if it's difficult to tell if gw is doing a good job, then the data isn't being presented very well.

i'm still weighing options for how to manage the automated price scanning system... i'll check into the draw issues.  it used to not play nice with auctioneer, but i think i fixed that.  maybe i've still got a forced ":Show()" in there from when the frame was its own window.

are you saying it doesn't list the recipe when your right click, or is the problem that you select it, but it doesn't seem to do anything?  the list that shows up is in order of preference, so if the ink recipe is before the vendor conversion, then it will try the ink recipe first.

the way the logic goes, gw will try each successive step to fill your needs.  it will use your known recipes to craft reagents that are craftable based on current inventories.  by "available" i mean in your bags, bank, etc or known to exist at the auction house.  if it can't craft something, it won't bother telling you to craft it (because it knows you can't given the current inventory of items).  it's late, i hope that made sense.

can you tell me a bit more about the details of the situation?  don't need the sv lua just yet.

hevreka, all recipes in the queue are changeable via a right click.  so if you want to use some other recipe instead of an ink conversion, right click the ink conversion and select the direct ink creation.  if you view in the flat layout, you can hit all inks of the same variety at one time.

yeoman, the reason that recipe is showing up is because you've visited the trainer has recorded that it will be available at 470.  since you are currently at 469 and have a 100% skill up recipe queued up (int on cloak), gw is predicting that you will be 470 and so it will show that 470 skill recipe as being orange (instead of red).  the idea being that as you queue recipes, gw will let you queue up recipes you haven't learned yet so that you can plan ahead when power leveling.

cantar, in the "details frame" (lower left) you can shift-click on the recipe name to link to chat.  i've reserved modified clicks in the skill list for group manipulations and multi-selecting (to be activated soon, i hope).