WowAce

It's an interesting feature. That guy has been pretty good about indirect detection of data like this. I'm not sure I can replicate it without wholesale lifting of his code which may not be the best route. I'll have to at least understand the math and memory requirements for something like this.

The information I want to know about is right in the quoted text of my last comment, especially the bit about monitor size/resolution/type. :)

The reason I don't think scaling is the right answer on making the window smaller and more usable is this sentence from Cokedriver: For me its really tight without having the UI set back so far i have to squint to see the text.

That tells me that scaling isn't going to work in his case to make the room required. The reason why scaling is really for me the last option is that I shouldn't require a user to set a scaling factor on their whole UI that they want, and then apply another one onto my addon that is needed to make it work. It isn't a good user experience, and is a bit of an admission that my UI may not be up to snuff in a certain environment. It may be a standard feature in various addons, but I have to ask myself why are all these addons using it, and what user scenarios are actually fixed by it? How many are scaling, and how many are resizing (which is ironically harder than scaling to get right in WoW)? Does it actually address the problems my users are seeing?

However, if I can get information on the size/resolution of the monitors people are having trouble with, and what they have their UI scaling set to (if they do that at all), I can at least replicate that on my own machines and see exactly what they are seeing as behavior. Then I can spend time tuning the window for those machines, and the UI will come out fine on the machines with larger monitors, giving them even more usable space on their screen.

And I responded directly to that request by asking for more detailed reasons why you felt it needed a scaling feature in the ticket. I never got a response. From the ticket:

Unfortunately, I'm not sure I agree adding a scaling option is the right way to fix a "window is too big" issue. If it is too big, it is too big, and that should be addressed instead of applying band-aids to it.

Now, I cant really do much with your ticket as-is. It tells me what to do, but none of the gritty details of why which are the most helpful part of a ticket like this. It is too big, sure, but how is it too big? Is it too wide, too tall, does it sit around the house? What size/type monitor do you play on?

I've made changes so the window can be collapsed by hiding the filters in the absence of good feedback on exactly what is wrong with the window. If this is not enough, feel free to give me these additional details so I can actually address the problem rather than guess.

And the reason I didn't think scaling was the answer is because of comments like Cokedriver's. To make it fit, the scaling option just makes the text even harder to read. Scaling helps those with high resolution, big monitors the most, the same people who are least likely to run into this problem.

I'm aware of the problem with engineering.

I've got a ticket open to track the work to manage which plugins are displayed in the list (which will let you hide the tools in the display). I've also got a couple ideas on how to make the list a bit shorter by only displaying what is needed, and shortening up the list to make it fit so you will get something like:

"Forge, Foo, Bar, 2 more..." rather than spewing junk all over the screen.

Can you Create a Ticket on that?

There's some weird behavior that is being driven by the client/server rather than addons at this point.

When you open a window, the data available is fed to the addon (even the official one) and then an Update event is sent to load the actual data. Part of the problem is that I'm trying to merge all update events within 1 second into a single event, and it's causing some lag and making this noticable.

Search should be unaffected by this once the initial update has taken place.

4.0.1 has changed quite a bit of the reality behind how tradeskill data is handled by the client, and has introduced bugs that I'm still flushing out. Some of them require a bit more time to fix than others, as includes more design-level decisions of what I should display before the initial update/etc...

Thanks for the kind words. I'm still annoyed that it took so long to track that particular issue down.

Try ProfessionTabs on WoWI... works well with MrTrader.

I forgot to attach a changelog to 0.6.1 so here's the changes:

* Fixes a bug with updating Categories and Inventory Slots
* Link behavior is closer to the official UI (can whisper the owner of a linked tradeskill).
* Search behavior is closer to the official UI (can search linked tradeskills and guild lists).
* Support for new guild functions, letting you look up who can craft certain guild recipes.