<deleted>

Kaitain · Post by **Kaitain** » Mon Apr 12, 2004 2:27 pm

ml2517 · Post by **ml2517** » Mon Apr 12, 2004 2:44 pm

You can get a list of windows with the /windows command also I believe.

Lax · Post by **Lax** » Mon Apr 12, 2004 3:19 pm

there's no apostrophe in possessive "its"

Any time inside [] you dont need "" unless you have a bracket in it. The quotes just get stripped anyway.

${Window[Enviro].Open} should work fine.

Kaitain · Post by **Kaitain** » Mon Apr 12, 2004 4:54 pm

Lax · Post by **Lax** » Mon Apr 12, 2004 10:57 pm

btw.,... please dont update your original post, look at it.. its ugly as shit

Windows dont have numbers, but item slots do. It's easier just to use the mnemonics though.

You can reference any backpack windows like "pack1" "pack2" "pack3" etc just like you do with itemnotify. Those and bank1-16 and "enviro".

So what you need to have is what pack # your sewing kit is, then do ${Window[pack1].Open}. Currently there's no quick and dirty way to find it but you can loop through ${Me.Inventory[pack@num].Name.Find[Sewing Kit]} (will find any "Sewing Kit" "Large Sewing Kit" etc, but you can also compare the Type i believe) until you find it. Keep that number and use it for all accesses..
${Window[pack@num]}, /itemnotify in pack@num 1 leftmouseup, /notify pack1 0 close

etc

wassup · Post by **wassup** » Tue Apr 13, 2004 12:09 am

We were talking about this in IRC...

Another way to find a specific type of container is using what you said Lax:

${Me.Inventory[@varName].Type.Equal[Jewelry Making]}

What I would be interested in seeing is finding a way to get the Pack Name (Like Tinkerer's Bag) using Window. One way we tried was using Tooltips, but it returned 'Container Name Here'.

dont_know_at_all · Post by **dont_know_at_all** » Tue Apr 13, 2004 12:14 am

More specifically:

${Window[ContainerWindow].Child[Container_Label].Text} returned 'Container Name Here''

For ${Window[TradeskillWnd].Child[COMBW_ContainerArea].Child[COMBW_ContainerName].Text}, I never got an answer.

Lax · Post by **Lax** » Tue Apr 13, 2004 12:33 am

The problem with using ContainerWindow is that it's just going to get you whichever container window was registered last, and if that specific one was unregistered, you're not going to get any container at all. For example, you open two containers... you can only possibly access one of those containers with this method. Let's assume you open one, and it gets registered... then you open the next, and it gets registered (both using "ContainerWindow").. you lose all access to the first one. Then you close the second one. Now ${Window[ContainerWindow].Open]} gives you NULL. So it's really not even a good indicator for the question "Do i have a container window open?". The same will be true for any window that uses the same template, such as chat windows and tip windows (there's tip of the day and there's context tips, both use the same template). Note that the buff and shortbuff windows use different templates though.

If you want to accurately use containers you should avoid using "ContainerWindow" and go with "pack1-8", "enviro", etc.

I'll do some thinking on this kind of issue to see about making it possible to access multiple windows using the same template. Problem, though, is the naming scheme will change slightly for the ones that werent open first (e.g. "ContainerWindow" "ContainerWindow2". I could also add something to MQ2Data to access a particular type of container, like ... ${Container[Jewelcraft]} .. and maybe add access to the item window from the item type... e.g. ${Me.Inventory[pack1].Window.Open}

Kaitain · Post by **Kaitain** » Tue Apr 13, 2004 8:32 am

<deleted>

<deleted>

Tradeskill Window Mode Flag