and document the return data structure so we can read fixed prices, suggested auctioneer prices, bid and sell, vendor buy and sell prices and deposit price. If enchantrix is present, also return its data. I'll look at kludging it in the meantime using a tooltip and pickup.
GetAuctioneerSearch(bag, slot)
Returns a data structure of auctions as per the search window. We need to know who the seller is, as well as item details.
_____________________________________
BatchPostOn Post(bag, slot, pricing) BatchPostOff
This would then let me queue posting requests with you that don't start posting until I have finished adding the items I wish to post. In the GUI, a Post Later / Post Now dropdown can trigger the queue processing when it changes to the Now state.
Speaking of posting, when you do your Pickup shouldn't that be a pickup? It would seem to avoid the GUI based problems I am having now when I attempt to post the next item (alt+click) too quickly.
Can you add these as three separate trac tickets, I'd love to implement them after I finish itemizer. Placing it on trac will make sure I don't forget.
As I am adding these as trac tickets, I will provide generalised workflow context here. I would imagine this is pretty standard.
I am wanting to back onto auctioneer as my 'sales tool'. However, I wish to write my own logic for whether I will post something and for how much.
Where [function] indicates an API call, my workflow would be this:
if [MinsSinceLastScan] > 60 then [Scan AH] [BatchPostOn]
Go through my bags, for each item:
[Request item search] How many are on sale? Am I in there?
[Request item stats] What is the auctioneer suggested sale price, median, history, my fixed price blah blah Perform some calculations on both of the above if selling then [Post item] item stats, stack size blah blah
http://auctioneeraddon.com/trac/ticket/949 New API: MinsSinceLastScan http://auctioneeraddon.com/trac/ticket/950 New API: ScanAH http://auctioneeraddon.com/trac/ticket/951 New API: BatchPostOn http://auctioneeraddon.com/trac/ticket/952 New API: BatchPostOff http://auctioneeraddon.com/trac/ticket/953 New API: Post(bag, slot, stacksize, sellprice, bidprice, expiry) http://auctioneeraddon.com/trac/ticket/954 New API: QueryItem(bag, slot)
My refactoring of the scanning engine and snapshot database will have some impact here:
MinsSinceLastScan - We will need to add a parameter to specify what item or items you are interested in. The parameter could be an itemKey (itemId:suffixId:enchantId), or be the query parameters. The reason being is that Auctioneer will be doing partial snapshot updates whenever queries are done on the AH (by the user directly or by scanning).
ScanAH - I've implemented such a thing already in the new scanning engine. You will be able to scan using any kind of search parameters Blizzard supports.
BatchPostOn and BatchPostOff - Rather than add these methods, I would like to see Auctioneer support the queuing of Post requests in general. In that case you would take a "snapshot" of the inventory and work off that. Either that your you make it an event driven state machine. Post one auction, wait for it to finish, move on to the next inventory item. That's actually how the posting enigne works with restacking items.
NumQueuedRequests - Once we support a queue this is easy.
Post - There is a similar method today, but it takes an itemKey (itemId:suffixId:enchantId) rather than a bag and slot. This is because the Auctioneer Post Auctions logic will do the inventory searching and stacking for you. It doesn't make sense to specify a bag and slot given the way it works.