WowAce

asesine, gw is supposed to track inventory on alts. there have been reports from others that it's not doing a great job in this regard, but i haven't yet delved into why that might be.

is it just a particular type of item not showing up or is it all items? when was the last time you deleted your gw sv file? deleting this file causes gw to have to "re-seed" the tracked item list which could create some lag into the tracking system.

do you get any items in the alt column if you view an alt from a different toon? that is, log in as toon X then view toon Y's tradeskills. does toon X have items that don't show up in the inventory column for toon Y?

oddible, if you change the queue layout to "flat" it should make all items in single runs by condensing all like recipes.

if you have lsw installed and enabled in the gw "plugins" pulldown, it should do pretty much everything lsw does in any other trade skill frame.  make sure you have the latest lsw.  is that what you're asking or am i misunderstanding the question?

yeoman, that is very useful info. it's telling me that the queue updating process is pretty much the only thing taking time to deal with. it's taking nearly 2 seconds to chew thru your queue each time it thinks it has to (which happens in at least 4 instances: inventory scan, auction scan, trade scan, and queue manipulations).

i suspect i can optimize the queue processing quite a bit, so that's good.

sprocket, jimi: i'll see what i can figure out with the inventory. keep in mind that "craftable" isn't just counting pigments you currently have, but pigments you can make as well from all your personal inventories (bag/bank/guildbank/mail/alts).

also, the way the recipe selection system works for the queue recipes is that the popup shows all the ways gw is actively looking to get the item you need and in the order it is looking. when you right click and change mill X to mill Y, it's just moving mill Y to be before mill X in the priority order. as it goes thru this list, it only counts instances where it can actually get/make that item from either you personal inventory or the auction house inventory. so if there are not enough Y herbs to satisfy your need, it'll move onto the next option to acquire the particular mat it's trying to acquire.

so you can change Mill Fadeleaf to Mill Peacebloom, but if there are no Peaceblooms to be found, it'll still say Mill Fadeleaf.

i am debating an option to turn off the auction house inventory consideration so that you can say "Mill Peacebloom" and it'll tell you to buy whatever Peaceblooms you still need if they aren't actually available.

sprocket, you can tell it to just buy the pigment by right-cliking the milling recipe and selecting "from auction" (should be the last option).  that will tell gw you want to buy the pigments and then you can pick the ones you want.  what i will probably add is some connect between the queue recipes and the auction tab so that you could also click on a recipe and have it filter the auction tab reagent frame to only list the reagents associated with this recipe.

so you could click "mill liferoot" and it would place in the reagent frame all the reagents for the sibling recipes (the other herbs that give the same pigment) as well as the item generated by the process (golden pigment).  i think this would make the comparison shopping a ton easier.

i'll think some more about how i could make it work from the shopping list.  the problem there is that a single reagent might be used in different queued recipes (herbs for milling vs alchemy, cloth for tailoring vs bandages, etc).  i suppose maybe there'd be a way around that, tho....

it's definitely a weak point right now with the system.

i could probably have it close automatically if it's empty.  the point of being a separate window is to allow you to have the queue open without having you screen completely filled while you operate on it.  you don't need the main window if you're just executing your queue or collecting your reagents.

once i get a config ui implemented, i'll make the window behavior adjustable.

also, hitting escape will close the main window and hitting it again will close the queue.

that sounds like the occasional "data isn't ready" kinds of errors that crop up occasionally when hitting some skills you haven't seen before.  did you get any report that the trade can was taking really long before it crashed?

for those interesting in helping be debug efficiency, the latest debug tool has a breakdown of each process that's associated with each message.  the data is pretty much the same for a process/message (iterations, elapsed, etc).  i've added the time of the most recent call to the table.

you can click on each function to fire it off individually just like you can for a message.

hopefully, this will help to determine what processes are chewing too many cycles so i can focus on them since it's hard for me to stress test like some of you guys with your glyph businesses and whatnot.

yeah, i mined that leveling data using trade links.  unfortunately, you can't generate trade links for smelting so i have to rely on wowhead/libpt data as a fallback.  just need to fold it into the system.

yeoman, i'm going to add some finer detail to isolate what's actually responding to the messages.  i'm surprised to see the skill rank change causes so many cycles to be burned.