Clean up help -- how to tell when windows are open

newb-n-training · Post by **newb-n-training** » Fri Apr 23, 2004 5:49 pm

Specifially I tried edting the sneakhide code to stop trying when either casting, at bank, at merchant, etc....

This is the only way I could do it but I particularly dont like the line w/ the windows but can't think of a better way to do it ... is there by chance one statement which would summarize all that ?

Code: Select all

Sub MySneakHide 
   /if (@sneakhide==1 && !${Me.Casting.ID}) {
     /if (${Window[BankWnd].Open}==0 && ${Window[BazaarWnd].Open}==0 && ${Window[BigBankWnd].Open}==0 && ${Window[GiveWnd].Open}==0 && ${Window[LootWnd].Open}==0 && ${Window[MerchantWnd].Open}==0 && ${Window[TradeskillWnd].Open}==0 && ${Window[TradeWnd].Open}==0) {
       /if (${Me.AbilityReady[Sneak]} && !${Me.Sneaking}) /doability "Sneak"
       /if (${Me.AbilityReady[Hide]}) /doability "Hide"
     }
   }
/return

Lax · Post by **Lax** » Fri Apr 23, 2004 7:00 pm

Nope, no one statement that will summarize all that. If we were to design something to do it, how exactly would we determine which windows qualify as you being "too busy" for whatever your macro happens to want to do at the moment? Carry on :)

newb-n-training · Post by **newb-n-training** » Fri Apr 23, 2004 7:39 pm

well said, and exactly what I feared ... but then there are many here who are much smarter than I so ... there's always hope

thanks again

Preocts · Post by **Preocts** » Sat Apr 24, 2004 8:42 am

pffft! Comeon Lax. Why can you just check for all the possible windows and states in the phraser before we try sneak hide or even forage. I mean just look at this mess in my macro.

Code: Select all

      /if (!${Me.Mount.ID} && !${Me.Casting.ID} && !${Window[SpellBookWnd].Open} && !${Me.Combat} && !${Window[LootWnd].Open} && !${Window[BigBankWnd].Open} && !${Cursor.Name.ID} && !${Window[MerchantWnd].Open}) {

...

...

I am so joking with you that if you take this seriously it's your own damn fault.

newb-n-training: It may look nasty but at least it is easier than what we used to have to do in the $param system.