GnomeWorks TradeSkill Frame -
a complete replacement for the blizzard trade skill frame.
early alpha just to test some things out.
You must login to post a comment. Don't have an account? Register to get one!
After I made that post I thought I might need to explain. I queue up anywhere from 50-100 glyphs at a time to process and I queue them by profitability. I can sort the profession window recipes by profitability but I would like to select multiple glyphs in a row and queue them all at once instead of having to manually select each glyph and queue them up singly.
So you said there should be an icon for cooking recipes that Overachiever tracks as missing for an achievement.
I don't see it with GW active
Uhm... I'm not sure, what you mean... You can select a recipe and enter an amount of items of that type to queue before hitting the "Queue"-Button. And you can queue different recipes one after the other.
So, what do you really mean?
Lilsparky, as far as I understand your posting (6 posts below this one...) you've created a work-around for the "Frame Level 128"-Bug? This problem is supposed to be "fixed" and should not happen again, right?
I'll take a good look at it. Hope you did it. :)
Hello. I was wondering if there was a way (and if not, if it can be implemented) to queue multiple items at once. I've tried everything I can think of to do it but no joy.
Last trade skill you were looking at would be fine for the single button. Once its open, I can go where I want.
how about if you select a recipe, it will open the main frame and jump to that recipe? it currently does this, but seems to fail if the recipe is from the last trade skill you were looking at. that should be easy enough to fix. the only problem with having the main window open from a single button is knowing which skill to show.
Somebody asked for a way to open the main frame from the queue frame and I'd like to second that request. How about adding the arrow tag like on the right of the main frame to left of the queue frame? With both open, the arrows are under the frames but when one is closed, the arrow to open the other is exposed.
I do remember seeing a bunch of messages about something being broken.
did it spit out a wad of messages about frame levels being broken? i probably just need to add the headers to the system that checks the levels.
the frame level "creep" seems to be related to how many frames are created. if you do "/framestack true" then it shows all the hidden frames as well. this implies that when you close a frame, it's still taking space in the frame level stack even tho it's not being used in any way. the frame levels are dynamic-ish. when a parent frame level increased/decreases, all the children increase/decrease by the same amount. or at least, they should.
as you open new windows, it creates new frames and ends up pushing your frame levels higher and higher. 129 needs to be the breaking point. i don't know why, but i do know that there's a quirk with frame levels where you can't manually move more than 128 frame levels in a single call. i think the two issues are related. i've given up on trying to debug the system and instead i'm just hacking in a test to see if the frames are ever behind their parent and if they are, they just move back ahead of them.