WoW BlueTracker Home | RSS | News | Contact
Recent | Search | Archive | CS Posts
Poster: Iriel at 10/11/2005 9:09:56 AM PDT
Subject: Upcoming 1.9 Changes - Concise List
   LUA Libraries
* bitlib will probably be in the WoW API as of 1.9 (Per slouken on 10/05)

Bug Fixes
* Better range checking on GetPlayerBuffApplications
<Addon Authors: Dont use RegisterForSave()!>

  http://forums.worldofwarcraft.com/thread.aspx?fn=wow-interface-customization&t=238150&p=#post238150
 
Poster: slouken at 10/12/2005 4:21:12 PM PDT
Subject: Re: Upcoming 1.9 Changes - Concise List
   Daedalus, come down... you're flying too high!
  http://forums.worldofwarcraft.com/thread.aspx?fn=wow-interface-customization&t=238150&p=#post241651
Poster: slouken at 10/12/2005 7:02:02 PM PDT
Subject: Re: Upcoming 1.9 Changes - Concise List
   Oops! :)
  http://forums.worldofwarcraft.com/thread.aspx?fn=wow-interface-customization&t=238150&p=#post241874
Poster: slouken at 10/13/2005 3:18:06 PM PDT
Subject: Re: Upcoming 1.9 Changes - Concise List
   The eighth return value of GetItemInfo() will no longer be localized, and will instead be a token from the following list:

"",
"INVTYPE_HEAD",
"INVTYPE_NECK",
"INVTYPE_SHOULDER",
"INVTYPE_BODY",
"INVTYPE_CHEST",
"INVTYPE_WAIST",
"INVTYPE_LEGS",
"INVTYPE_FEET",
"INVTYPE_WRIST",
"INVTYPE_HAND",
"INVTYPE_FINGER",
"INVTYPE_TRINKET",
"INVTYPE_WEAPON",
"INVTYPE_SHIELD",
"INVTYPE_RANGED",
"INVTYPE_CLOAK",
"INVTYPE_2HWEAPON",
"INVTYPE_BAG",
"INVTYPE_TABARD",
"INVTYPE_ROBE",
"INVTYPE_WEAPONMAINHAND",
"INVTYPE_WEAPONOFFHAND",
"INVTYPE_HOLDABLE",
"INVTYPE_AMMO",
"INVTYPE_THROWN",
"INVTYPE_RANGEDRIGHT",

You can get the localized text for each token by calling getglobal on the token (e.g.)
getglobal("INVTYPE_ROBE")

The other GetItemInfo() return values will remain localized.
  http://forums.worldofwarcraft.com/thread.aspx?fn=wow-interface-customization&t=238150&p=#post243063
Poster: slouken at 10/13/2005 3:41:47 PM PDT
Subject: Re: Request: Texture param for GetItemInfo
  

Q u o t e:
I have another request: add a texture return value to GetItemInfo().


You got it. The ninth return value will be an inventory icon.
  http://forums.worldofwarcraft.com/thread.aspx?fn=wow-interface-customization&t=238150&p=#post243098
Poster: slouken at 10/13/2005 4:01:16 PM PDT
Subject: Re: Upcoming 1.9 Changes - Concise List
  

Q u o t e:
As requested by a few of us, can we get the GameTooltipTemplate split into its own file?



Sure. :)
GameTooltipTemplate.xml

[ post edited by slouken ]

  http://forums.worldofwarcraft.com/thread.aspx?fn=wow-interface-customization&t=238150&p=#post243118
Poster: slouken at 10/13/2005 5:55:42 PM PDT
Subject: Re: Upcoming 1.9 Changes - Concise List
   I'm afraid to ask what you need a hashing algorithm for...
  http://forums.worldofwarcraft.com/thread.aspx?fn=wow-interface-customization&t=238150&p=#post243233
Poster: slouken at 10/14/2005 9:42:15 AM PDT
Subject: Re: Upcoming 1.9 Changes - Concise List
   Added Texture:GetTexure(), which returns the filename of the texture, without extension, if there is one. If the texture couldn't be loaded, is a color texture, or hasn't been set, this function will return nil.

Note that Texture:SetTexture() does it's own internal checking so it's actually more efficient to blindly set the same file multiple times than it is to query the existing filename and compare it with the desired one.
  http://forums.worldofwarcraft.com/thread.aspx?fn=wow-interface-customization&t=238150&p=#post243842
Poster: slouken at 10/14/2005 9:46:02 AM PDT
Subject: Re: Upcoming 1.9 Changes - Concise List
   Added FontString:SetNonSpaceWrap(true|false)
  http://forums.worldofwarcraft.com/thread.aspx?fn=wow-interface-customization&t=238150&p=#post243847
Poster: slouken at 10/14/2005 10:38:35 AM PDT
Subject: Re: Upcoming 1.9 Changes - Concise List
  

Q u o t e:
Hey, I told you to stay outta that thread!



What thread? :)
  http://forums.worldofwarcraft.com/thread.aspx?fn=wow-interface-customization&t=238150&p=#post243902
Poster: slouken at 10/14/2005 9:42:15 AM PDT
Subject: Re: Upcoming 1.9 Changes - Concise List *edited post*
   Added Texture:GetTexture(), which returns the filename of the texture, without extension, if there is one. If the texture couldn't be loaded, is a color texture, or hasn't been set, this function will return nil.

Note that Texture:SetTexture() does it's own internal checking so it's actually more efficient to blindly set the same file multiple times than it is to query the existing filename and compare it with the desired one.

[ post edited by slouken ]

  http://forums.worldofwarcraft.com/thread.aspx?fn=wow-interface-customization&t=238150&p=#post243842
Poster: slouken at 10/14/2005 12:08:22 PM PDT
Subject: Re: Upcoming 1.9 Changes - Concise List
  

Q u o t e:
You're missing a 't' in GetTexture!


Oh right, typo in my post, not the code. :)
  http://forums.worldofwarcraft.com/thread.aspx?fn=wow-interface-customization&t=238150&p=#post244001
Poster: slouken at 10/14/2005 12:14:41 PM PDT
Subject: Re: Upcoming 1.9 Changes - Concise List
   Added Frame:GetFrameType() and Frame:IsFrameType("type")

The distinct frame types are:
Button
CheckButton
EditBox
Frame
MessageFrame
Model
ScrollFrame
ScrollingMessageFrame
Slider
SimpleHTML
StatusBar
ColorSelect
GameTooltip
Minimap
PlayerModel
DressUpModel
TabardModel
LootButton

Note that a button, for example would return "Button" from GetFrameType(), but would return true for both IsFrameType("button") and IsFrameType("frame"), since all of the frame functions are also usable on buttons.

[ post edited by slouken ]

  http://forums.worldofwarcraft.com/thread.aspx?fn=wow-interface-customization&t=238150&p=#post244011
Poster: slouken at 10/14/2005 1:46:21 PM PDT
Subject: Re: Upcoming 1.9 Changes - Concise List
  

Q u o t e:
Can we get some kind of function to tell us bonuses on an item? This fudging the tooltip and parsing it's text is kinda silly. I would think it would basically just amount to taking the existing function(s) that is called in tooltip:SetInventoryItem and making it available.



No.
  http://forums.worldofwarcraft.com/thread.aspx?fn=wow-interface-customization&t=238150&p=#post244152
Poster: slouken at 10/14/2005 2:39:28 PM PDT
Subject: Re: Upcoming 1.9 Changes - Concise List
   Added a new LoadWith keyword to the addon .toc file.
e.g.
## LoadOnDemand: 1
## LoadWith: Blizzard_AuctionUI
This would cause the addon to be loaded after the Blizzard auction UI had been loaded, but before the auction UI is opened.

There are some important things to know here:
1. You can specify any number of addons, and your addon will be loaded after the first of any of them load.
2. Your addon can be manually loaded without any of the addons you're interested in are loaded, so be sure to check to make sure the addon you want is loaded before doing any work. If it isn't you should wait for the ADDON_LOADED event for the addon you're interested in.
3. If one of the addons you load with is not loaded on demand, then your addon will load immediately after it in the login addon load sequence.
  http://forums.worldofwarcraft.com/thread.aspx?fn=wow-interface-customization&t=238150&p=#post244218
Poster: slouken at 10/14/2005 2:46:37 PM PDT
Subject: Re: Upcoming 1.9 Changes - Concise List
   Okay, the party's over, I'm going back to regular (non-UI) work. :)

*picks up his swatter*
*splat* ... *splat* ... Ewww, that was a big one...

[ post edited by slouken ]

  http://forums.worldofwarcraft.com/thread.aspx?fn=wow-interface-customization&t=238150&p=#post244226
Poster: slouken at 10/16/2005 11:44:42 AM PDT
Subject: Re: Upcoming 1.9 Changes - Concise List
   I'm pretty sure that exact matches have priority over partial matches... do you have an example where that isn't the case?
  http://forums.worldofwarcraft.com/thread.aspx?fn=wow-interface-customization&t=238150&p=#post245579
Poster: slouken at 10/18/2005 9:54:17 AM PDT
Subject: Re: Upcoming 1.9 Changes - Concise List
  

Q u o t e:
Slouken, "Strong Anti-Venom" still thinks I dont have enough mana to use it (Regular Anti-Venom is fine)


I just tried this, and it worked fine for me. I stuck a stack of 3 of them in the first slot (where the attack icon usually is) and then checked the return value of IsUsableAction(1), and it returned 1, nil - which means usable, and not out of mana.
  http://forums.worldofwarcraft.com/thread.aspx?fn=wow-interface-customization&t=238150&p=#post247022
Poster: slouken at 10/19/2005 4:30:41 PM PDT
Subject: Re: Upcoming 1.9 Changes - Concise List
  

Q u o t e:
Hey Slouken, is there any chance of getting a 6 or 8 parameter version of SetTexCoord to allow for (minimally) shearing or (maximally) any linear transformation?


Sure:

// Origin is upper left, vertices specified:
//
// 0 2
//
// 1 3
//
SetTexCoord(ULx, ULy, LLx, LLy, URx, URy, LRx, LRy)

You'll have to test this when 1.9 hits the test server.
  http://forums.worldofwarcraft.com/thread.aspx?fn=wow-interface-customization&t=238150&p=#post248160
Poster: slouken at 10/19/2005 4:33:01 PM PDT
Subject: Re: Upcoming 1.9 Changes - Concise List
   In 1.9, per-character settings will be per-realm as well, saved in the directory:
WTF\Account\{account}\{realm}\{character}\

Per-character settings will be loaded from the old location if they can't be found in the new location, for backwards compatibility.
  http://forums.worldofwarcraft.com/thread.aspx?fn=wow-interface-customization&t=238150&p=#post248162
Poster: slouken at 10/19/2005 5:04:01 PM PDT
Subject: Re: Upcoming 1.9 Changes - Concise List
   Erm.. no..

Argh... that's going to hose saved variables which are reset to defaults and the empty file is then removed. Perhaps I'll leave the empty file there after all...
  http://forums.worldofwarcraft.com/thread.aspx?fn=wow-interface-customization&t=238150&p=#post248182
Poster: slouken at 10/20/2005 2:19:45 PM PDT
Subject: Re: Upcoming 1.9 Changes - Concise List
  

Q u o t e:

When there is no "## SavedVariables" entry in the .toc, or there is one but it says "## SavedVariables: " with no variables specified, WoW should purge the account-level savedvar file on logout.



Good point. This is how it will work in 1.9.
  http://forums.worldofwarcraft.com/thread.aspx?fn=wow-interface-customization&t=238150&p=#post248863
Poster: slouken at 10/20/2005 2:24:23 PM PDT
Subject: Re: Upcoming 1.9 Changes - Concise List
  

Q u o t e:
The only problem will be that for a person with multiple characters, only one of the characters would maintain a copy of the AddOns variables.



That's correct, if an author switches a variable from account-wide to per-character. But you'll note that's the case even in the current situation if there are still account wide variables in use; the per-character variable would get written to the per-character file, and the account-wide file would get saved without the per-character variable.
  http://forums.worldofwarcraft.com/thread.aspx?fn=wow-interface-customization&t=238150&p=#post248870
Poster: slouken at 10/20/2005 2:19:45 PM PDT
Subject: Re: Upcoming 1.9 Changes - Concise List *edited post*
  

Q u o t e:

When there is no "## SavedVariables" entry in the .toc, or there is one but it says "## SavedVariables: " with no variables specified, WoW should purge the account-level savedvar file on logout.



Good point. This is how it will work in 1.9.
  http://forums.worldofwarcraft.com/thread.aspx?fn=wow-interface-customization&t=238150&p=#post248863
Poster: slouken at 10/20/2005 2:24:23 PM PDT
Subject: Re: Upcoming 1.9 Changes - Concise List *edited post*
  

Q u o t e:
The only problem will be that for a person with multiple characters, only one of the characters would maintain a copy of the AddOns variables.



That's correct, if an author switches a variable from account-wide to per-character. But you'll note that's the case even in the current situation if there are still account wide variables in use; the per-character variable would get written to the per-character file, and the account-wide file would get saved without the per-character variable.
  http://forums.worldofwarcraft.com/thread.aspx?fn=wow-interface-customization&t=238150&p=#post248870
Poster: slouken at 10/21/2005 6:38:22 PM PDT
Subject: Re: Upcoming 1.9 Changes - Concise List
   Macros: Good News and Bad News

The Bad News:
The game will be enforcing the limit of 18 macros.

The Good News:
There is now an additional 18 macros available for each character.
  http://forums.worldofwarcraft.com/thread.aspx?fn=wow-interface-customization&t=238150&p=#post249885
Poster: slouken at 10/24/2005 12:40:20 PM PDT
Subject: Re: Upcoming 1.9 Changes - Concise List
   Iriel, just to correct your entry, there are still 18 global macros. There are now 18 additional character-specific macros (which are indexed 19-36 in the API)
  http://forums.worldofwarcraft.com/thread.aspx?fn=wow-interface-customization&t=238150&p=#post251531
Poster: slouken at 10/26/2005 12:12:50 PM PDT
Subject: Re: Upcoming 1.9 Changes - Concise List
   In 1.9, debugprofilestart() and debugprofilestop() will have sub-millisecond floating point precision.

For those who don't know, you can call debugprofilestart(), and then the next call to debugprofilestop() will return the elapsed time in milliseconds since the last call to debugprofilestart().
  http://forums.worldofwarcraft.com/thread.aspx?fn=wow-interface-customization&t=238150&p=#post252865
Poster: slouken at 10/29/2005 11:08:04 AM PDT
Subject: Re: Upcoming 1.9 Changes - Concise List
  

Q u o t e:
Still no chance of a way for variables to be saved/loaded per realm, but shared across characters? I keep multiple active characters on multiple realms, and for the likes of Auctioneer, RecipeBook, and CharactersViewer (which all benefit from sharing data among characters on a realm) to have to load all their data from other realms even though it's irrelevant is a big memory / login time hit.


You can do this, but you have to code it yourself. :)
  http://forums.worldofwarcraft.com/thread.aspx?fn=wow-interface-customization&t=238150&p=#post254552
Poster: slouken at 10/31/2005 12:04:55 PM PST
Subject: Re: Upcoming 1.9 Changes - Concise List
   You'd have to use the global variables, which isn't any worse than the current system.

We're not going to add support for more fine grained variable saving. Global and per-character is it. (Combinations suggested included per-class configuration data, and an option for the old style per-character data, etc. etc.)
  http://forums.worldofwarcraft.com/thread.aspx?fn=wow-interface-customization&t=238150&p=#post255483
Poster: slouken at 10/31/2005 12:05:29 PM PST
Subject: Re: Upcoming 1.9 Changes - Concise List
  

Q u o t e:
Will SPELLCAST_STOP ever get an argument that returns the spell name?



Not as far as I know.
  http://forums.worldofwarcraft.com/thread.aspx?fn=wow-interface-customization&t=238150&p=#post255485
Poster: slouken at 11/7/2005 1:52:50 PM PST
Subject: Re: Upcoming 1.9 Changes - Concise List
   In 1.9, saved variables will only load from the appropriate directory; saved variables files in the main game directory will not override the ones saved by the game.
  http://forums.worldofwarcraft.com/thread.aspx?fn=wow-interface-customization&t=238150&p=#post259528
Poster: slouken at 11/7/2005 3:49:15 PM PST
Subject: Re: Upcoming 1.9 Changes - Concise List
   In 1.9, the game will no longer accidentally load UI files that are dropped loose into the top level installation directory.
  http://forums.worldofwarcraft.com/thread.aspx?fn=wow-interface-customization&t=238150&p=#post259627
Poster: slouken at 11/10/2005 5:45:19 PM PST
Subject: Re: Upcoming 1.9 Changes - Concise List
   Thanks to Esamynn, I looked into why occasionally some frames didn't have their layout available at login.

This led step by step into a massive optimization of the layout engine for 1.9. This resulted in the following visible changes:
* The game should load faster
* Greatly improved the scrolling speed for the TOS and EULA
* Querying the points on a hidden frame will cause the layout engine to resolve the frame's layout and (hopefully) return valid information.
* Like frames, textures and fontstrings now have an IsShown() method, which returns true if the texture or string would be visible if the frame that owns it is visible, and like frames, IsVisible() will return false if the frame that owns it is not visible.
* Bugs (Never!)
  http://forums.worldofwarcraft.com/thread.aspx?fn=wow-interface-customization&t=238150&p=#post261745
Poster: slouken at 11/10/2005 7:12:08 PM PST
Subject: Re: Upcoming 1.9 Changes - Concise List
   Oh, another change:
As part of the optimization pass, inherited children are instantiated only after the entire frame is loaded from XML. This means that you can't anchor layer elements to inherited children (you couldn't anchor to normal children before either).

The Blizzard UI scrolling frames are getting their scrollbar textures re-anchored to account for this.
  http://forums.worldofwarcraft.com/thread.aspx?fn=wow-interface-customization&t=238150&p=#post261788
Poster: slouken at 11/10/2005 8:19:36 PM PST
Subject: Re: Upcoming 1.9 Changes - Concise List
  

Q u o t e:
Just to confirm - They ARE instantiated before the OnLoad of the inheriting frame is fired?


Yes.
  http://forums.worldofwarcraft.com/thread.aspx?fn=wow-interface-customization&t=238150&p=#post261825
Poster: slouken at 11/10/2005 8:43:19 PM PST
Subject: Re: Upcoming 1.9 Changes - Concise List
   How about just "Optimization of the frame layout engine", instead of MASSIVE.. :)
  http://forums.worldofwarcraft.com/thread.aspx?fn=wow-interface-customization&t=238150&p=#post261838
Poster: slouken at 11/11/2005 5:46:27 PM PST
Subject: Re: Upcoming 1.9 Changes - Concise List
  

Q u o t e:
Imagine a virtual frame called MyTemplateFrame, which has a bunch of Textures arranged in some shape, let's call them MyTemplateFrameTop, MyTemplateFrameBottom, MyTemplateFrameMiddle, etc.

Now you create YourFrame, which inherits from MyTemplateFrame, and has its own Textures declared in the XML, you cannot anchor those to MyTemplateFrameMiddle (or the other ones) in the XML code, you'd have to do it programatically in YourFrame's OnLoad function.

Did that help (and slouken - did I get that right?)


Almost...
In your example you could anchor textures to MyTemplateFrameMiddle, but if there was a frame MyTemplateChild, you couldn't anchor the textures to that. If you had a child frame, your child frame could anchor to it though.
  http://forums.worldofwarcraft.com/thread.aspx?fn=wow-interface-customization&t=238150&p=#post262493
Poster: slouken at 11/11/2005 7:56:40 PM PST
Subject: Re: Upcoming 1.9 Changes - Concise List
   It's actually (including the OnLoad/OnShow handlers):

A few attributes of InstanceFrame (like name)
VirtualFrame
InstanceFrame
$parentChild (As InstanceFrameChild)
InstanceFrameChild:OnLoad()
InstanceFrameChild:OnShow()
$parentChild2 (As InstanceFrameChild2)
InstanceFrameChild2:OnLoad()
InstanceFrameChild2:OnShow()
InstanceFrameChild3
InstanceFrameChild3:OnLoad()
InstanceFrameChild3:OnShow()
InstanceFrameChild4
InstanceFrameChild4:OnLoad()
InstanceFrameChild4:OnShow()
InstanceFrame:OnLoad()
InstanceFrame:OnShow()

[ post edited by slouken ]

  http://forums.worldofwarcraft.com/thread.aspx?fn=wow-interface-customization&t=238150&p=#post262537
Poster: slouken at 11/11/2005 8:37:52 PM PST
Subject: Re: Upcoming 1.9 Changes - Concise List
   Hey, you should probably mention that you should never do this:
UIParent:SetFrameStrata("TOOLTIP")

*grin*

In general, you shouldn't be changing the frame strata of any frame. It's really something that should only be set once. It's particularly important that you don't change the frame strata of WorldFrame or UIParent.
  http://forums.worldofwarcraft.com/thread.aspx?fn=wow-interface-customization&t=238150&p=#post262544
Poster: slouken at 11/11/2005 5:46:27 PM PST
Subject: Re: Upcoming 1.9 Changes - Concise List *edited post*
  

Q u o t e:
Imagine a virtual frame called MyTemplateFrame, which has a bunch of Textures arranged in some shape, let's call them MyTemplateFrameTop, MyTemplateFrameBottom, MyTemplateFrameMiddle, etc.

Now you create YourFrame, which inherits from MyTemplateFrame, and has its own Textures declared in the XML, you cannot anchor those to MyTemplateFrameMiddle (or the other ones) in the XML code, you'd have to do it programatically in YourFrame's OnLoad function.

Did that help (and slouken - did I get that right?)


Almost...
In your example you could anchor textures to MyTemplateFrameMiddle, but if there was a frame MyTemplateChild, you couldn't anchor the textures to that. If you had a child frame, your child frame could anchor to it though.
  http://forums.worldofwarcraft.com/thread.aspx?fn=wow-interface-customization&t=238150&p=#post262493
Poster: slouken at 11/11/2005 7:56:40 PM PST
Subject: Re: Upcoming 1.9 Changes - Concise List *edited post*
   It's actually (including the OnLoad/OnShow handlers):

A few attributes of InstanceFrame (like name)
VirtualFrame
InstanceFrame
$parentChild (As InstanceFrameChild)
InstanceFrameChild:OnLoad()
InstanceFrameChild:OnShow()
$parentChild2 (As InstanceFrameChild2)
InstanceFrameChild2:OnLoad()
InstanceFrameChild2:OnShow()
InstanceFrameChild3
InstanceFrameChild3:OnLoad()
InstanceFrameChild3:OnShow()
InstanceFrameChild4
InstanceFrameChild4:OnLoad()
InstanceFrameChild4:OnShow()
InstanceFrame:OnLoad()
InstanceFrame:OnShow()

[ post edited by slouken ]

  http://forums.worldofwarcraft.com/thread.aspx?fn=wow-interface-customization&t=238150&p=#post262537
Poster: slouken at 11/11/2005 8:37:52 PM PST
Subject: Re: Upcoming 1.9 Changes - Concise List *edited post*
   Hey, you should probably mention that you should never do this:
UIParent:SetFrameStrata("TOOLTIP")

*grin*

In general, you shouldn't be changing the frame strata of any frame. It's really something that should only be set once. It's particularly important that you don't change the frame strata of WorldFrame or UIParent.
  http://forums.worldofwarcraft.com/thread.aspx?fn=wow-interface-customization&t=238150&p=#post262544
Poster: slouken at 11/14/2005 3:41:28 PM PST
Subject: Re: Upcoming 1.9 Changes - Concise List
  

Q u o t e:
Slouken, would it be possible to return a new 10th param from GetItemInfo() that returns the item's level?


No. The item level is typically 5 levels higher than the required level, which is already returned.
  http://forums.worldofwarcraft.com/thread.aspx?fn=wow-interface-customization&t=238150&p=#post264108
Poster: slouken at 11/16/2005 9:47:59 AM PST
Subject: Re: Upcoming 1.9 Changes - Concise List
   Added Button:SetFont("font", fontHeight [, flags]), which works exactly like the FontString function of the same name.
  http://forums.worldofwarcraft.com/thread.aspx?fn=wow-interface-customization&t=238150&p=#post265353
Poster: slouken at 11/16/2005 11:37:28 AM PST
Subject: Re: Upcoming 1.9 Changes - Concise List
  

Q u o t e:
Will the saved macro's still be stored in the macros-cache.txt and macros-local.txt files, or will they be saved in Blizzard_MacroUI saved variables files?


They will be saved in macros-cache.txt in the account directory and character directory respectively.
  http://forums.worldofwarcraft.com/thread.aspx?fn=wow-interface-customization&t=238150&p=#post265417
Poster: slouken at 11/16/2005 2:49:26 PM PST
Subject: Re: Upcoming 1.9 Changes - Concise List
   Added ScrollingMessageFrame:SetFont("font", fontHeight [, flags]), which works exactly like the FontString function of the same name.
  http://forums.worldofwarcraft.com/thread.aspx?fn=wow-interface-customization&t=238150&p=#post265572
Poster: slouken at 11/16/2005 3:15:43 PM PST
Subject: Re: Upcoming 1.9 Changes - Concise List
  

Q u o t e:

Improved parent graph checking to avoid parent loops (client crash)



You should probably just say instead that creating circular layout dependencies will generate a Lua error instead of crashing. :)
  http://forums.worldofwarcraft.com/thread.aspx?fn=wow-interface-customization&t=238150&p=#post265592
Poster: slouken at 11/18/2005 9:27:48 AM PST
Subject: Re: Upcoming 1.9 Changes - Concise List
   Yes, that's right.
  http://forums.worldofwarcraft.com/thread.aspx?fn=wow-interface-customization&t=238150&p=#post266637
Poster: slouken at 11/22/2005 12:07:09 PM PST
Subject: Re: Upcoming 1.9 Changes - Concise List
   Added Frame:GetEffectiveScale()
Since Frame:GetScale() now returns the value set with Frame:SetScale(), Frame:GetEffectiveScale() can be used to get the cumulative scale calculated using the parent scale.

Basically, all existing calls to Frame:GetScale() should probably use Frame:GetEffectiveScale() now.
  http://forums.worldofwarcraft.com/thread.aspx?fn=wow-interface-customization&t=238150&p=#post268675
Poster: slouken at 11/23/2005 9:45:42 AM PST
Subject: Re: Upcoming 1.9 Changes - Concise List
  

Q u o t e:

Or alternatively, change UnregisterEvent so that if it is called with no arguments then it unregisters all the events that a frame is currently registered for.


Sure, I added Frame:UnregisterAllEvents() for 1.9
  http://forums.worldofwarcraft.com/thread.aspx?fn=wow-interface-customization&t=238150&p=#post269180
Poster: slouken at 11/23/2005 9:59:41 AM PST
Subject: Re: Upcoming 1.9 Changes - Concise List
   BTW, Frame:GetEffectiveScale() and Frame:UnregisterAllEvents() are not on the test realm yet.
  http://forums.worldofwarcraft.com/thread.aspx?fn=wow-interface-customization&t=238150&p=#post269189
Poster: slouken at 11/23/2005 11:25:33 AM PST
Subject: Re: Upcoming 1.9 Changes - Concise List
  

Q u o t e:
Does Frame:UnregisterAllEvents() affect only Frame or both Frame and all of its children and their children's children, and so on?


It only affects the frame.
  http://forums.worldofwarcraft.com/thread.aspx?fn=wow-interface-customization&t=238150&p=#post269243
Poster: slouken at 11/23/2005 6:51:43 PM PST
Subject: Re: Upcoming 1.9 Changes - Concise List
  

Q u o t e:
For the new per-character addon functions, do they only operate for characters on the current Realm?



Hmm? I'm not sure what you mean...


Q u o t e:

(PS.. HUGE thanks for making all those settings realm+char name and not just char name)


You're welcome!
  http://forums.worldofwarcraft.com/thread.aspx?fn=wow-interface-customization&t=238150&p=#post269417
Poster: slouken at 11/23/2005 6:53:33 PM PST
Subject: Re: Upcoming 1.9 Changes - Concise List
  

Q u o t e:
Hey Slouken - You'll be happy to know that so far the new SetTexCoord seems to behave perfectly!



Great!


Q u o t e:

Will Texture objects always split into 2 triangles predictably (i.e. UL-UR-LL / UR-LR-LL) ?


Yes, I believe so.
  http://forums.worldofwarcraft.com/thread.aspx?fn=wow-interface-customization&t=238150&p=#post269418
Poster: slouken at 11/23/2005 6:54:34 PM PST
Subject: Re: Upcoming 1.9 Changes - Concise List
  

Q u o t e:
The multiline edit box bug appears fixed on text :) That's where an unbroken line would truncate (...) and not show anything afterwards.

Thanks Slouken!


You're welcome! :)
  http://forums.worldofwarcraft.com/thread.aspx?fn=wow-interface-customization&t=238150&p=#post269420
Poster: slouken at 11/23/2005 6:55:05 PM PST
Subject: Re: Upcoming 1.9 Changes - Concise List
  

Q u o t e:
Slouken, here is a very minor style bug with the new shiny AddOn selection screen. Use of the word "mod" in GlueXML, in GlueStrings.lua:

ENABLED_FOR_SOME = "This mod is only enabled for some characters.";

I beleive this should be "AddOn" and not "mod".


Thanks, I forwarded this along...
  http://forums.worldofwarcraft.com/thread.aspx?fn=wow-interface-customization&t=238150&p=#post269421
Poster: slouken at 11/23/2005 7:43:19 PM PST
Subject: Re: Upcoming 1.9 Changes - Concise List
  

Q u o t e:
Slouken, Blizzard Lua codes that use GetScale!

There are some, most notably MouseIsOver() in UIParent.lua. At the moment, this function is broken, since with patch 1.9 :GetScale() returns relative and not absolute scale. I beleive that MouseIsOver in particular should be changed to use the new GetEffectiveScale().



Yes, this was actually what GetEffectiveScale() was added for, but neither that, nor the Lua fixes made it onto the test server. They will be available in a future test server update.

Thanks though! :)
  http://forums.worldofwarcraft.com/thread.aspx?fn=wow-interface-customization&t=238150&p=#post269452
Poster: slouken at 11/23/2005 9:29:18 PM PST
Subject: Re: Upcoming 1.9 Changes - Concise List
  

Q u o t e:
According to the usage info we have:

EnableAddOn ("character", index) (index or "name")

I have an Iriel on Dark Iron, as well as Silver Hand.

If I do

EnableAddOn("Iriel", 1)

is it the one on the current realm? both? an arbitrary one? The behaviour of the AddOn menu on the character select screen appears to be that it's limited to the current realm.


It's the one from the current realm. I'm trying to remember whether you can actually modify addons for other characters from in-game. I think the EnableAddOn() function in-game takes different parameters than the one at the addon settings screen, but I'm not sure. I'll take a look later...

[ post edited by slouken ]

  http://forums.worldofwarcraft.com/thread.aspx?fn=wow-interface-customization&t=238150&p=#post269485
Poster: slouken at 11/28/2005 10:16:26 AM PST
Subject: Re: Upcoming 1.9 Changes - Concise List
  

Q u o t e:
It would be nice if when one or both of the arguments to UnitIsUnit are nil that it would simply return false/nil instead of generating an error.


When would you ever legitimately pass nil to UnitIsUnit()?

If you have a special case you're dealing with, you could just code the following:
if ( unit1 and unit2 and UnitIsUnit(unit1, unit2) ) then ... end

[ post edited by slouken ]

  http://forums.worldofwarcraft.com/thread.aspx?fn=wow-interface-customization&t=238150&p=#post271250
Poster: slouken at 11/28/2005 1:27:49 PM PST
Subject: Re: Upcoming 1.9 Changes - Concise List
  

Q u o t e:
Perhaps always return nil/false if either of the units doesn't exists?

For instance: UnitIsUnit("raid1", "raid2") return 1 if you're not in a raid.


Sure. This will be in the next 1.9 test realm update. However, this will mean that UnitIsUnit("target", "target") will return false as well, if you don't have anyone targeted. (Not that I think that will break anything, but fyi...)
  http://forums.worldofwarcraft.com/thread.aspx?fn=wow-interface-customization&t=238150&p=#post271354
Poster: slouken at 11/28/2005 3:18:41 PM PST
Subject: Re: Upcoming 1.9 Changes - Concise List
  

Q u o t e:
Slouken - how difficult would it be on your end to add double-wide screen resolutions to the list?


It's on our TODO list at some point. Please remind me in a month or so to look into it.
  http://forums.worldofwarcraft.com/thread.aspx?fn=wow-interface-customization&t=238150&p=#post271428
Poster: slouken at 12/1/2005 1:46:49 PM PST
Subject: Re: Upcoming 1.9 Changes - Concise List
   Good grief, enough with the UnitIsUnit() discussion. The change has been made. If it causes significant real-world problems, please let me know.
  http://forums.worldofwarcraft.com/thread.aspx?fn=wow-interface-customization&t=238150&p=#post273278
Poster: slouken at 12/2/2005 10:13:01 AM PST
Subject: Re: Upcoming 1.9 Changes - Concise List
  

Q u o t e:
Any chance of getting

local font,fontSize,flags = FontString:GetFont()

Someday?


Sure.
Added EditBox:SetFont()
Added GetFont() methods to match the existing SetFont() script methods.
  http://forums.worldofwarcraft.com/thread.aspx?fn=wow-interface-customization&t=238150&p=#post273702
Poster: slouken at 12/2/2005 11:08:15 AM PST
Subject: Re: Upcoming 1.9 Changes - Concise List
   1.9
  http://forums.worldofwarcraft.com/thread.aspx?fn=wow-interface-customization&t=238150&p=#post273730
Poster: slouken at 12/4/2005 8:05:50 AM PST
Subject: Re: Upcoming 1.9 Changes - Concise List
  

Q u o t e:
According to the test realm patch notes, 0.9 "Optimized UI event handling in raid situations."

What do these changes involve? Is this dealing with how the blizzard raid UI handles events, how the client generates events, or both?



Both. Health updates were being sent twice, in some circumstances, and the raid UI now only registers for the events it needs when it's active.
  http://forums.worldofwarcraft.com/thread.aspx?fn=wow-interface-customization&t=238150&p=#post274551
Poster: slouken at 12/8/2005 2:42:58 PM PST
Subject: Re: Upcoming 1.9 Changes - Concise List
   Added debugstack([start] [, count1] [, count2])
This function returns a string representation of the current calling stack, similar to the output of the normal Lua debug.traceback() call.
The parameter 'start' is the function level to start the stack trace, which defaults to 1 (the function that called debugstack()).
The parameter 'count1' is the number of function calls to show in the first part of the stack trace, which defaults to 12.
The parameter 'count2' is the number of function calls to show in the second part of the stack trace, which defaults to 10.
If there are more than count1+count2 calls in the stack trace, they are separated by "..."

For example, if you had the following call chain:
debugstack(2, 1, 3)
a()
b()
c()
d()
e()
f()
g()
(g calls f calls e, etc.)
The output would show b, ..., e, f, g

[ post edited by slouken ]

  http://forums.worldofwarcraft.com/thread.aspx?fn=wow-interface-customization&t=238150&p=#post277092
Poster: slouken at 12/8/2005 3:06:11 PM PST
Subject: Re: Upcoming 1.9 Changes - Concise List
  

Q u o t e:

UnitIsUnit(x,y) will return nil if either of the units does not presently exist (Even if x==y)



It's actually implemented like this:
if(x == y) return true
if(!*x) return false
if(*x == *y) return true
  http://forums.worldofwarcraft.com/thread.aspx?fn=wow-interface-customization&t=238150&p=#post277112
Poster: slouken at 1/3/2006 3:32:44 PM PST
Subject: Re: Upcoming 1.9 Changes - Concise List
   Hey Iriel, want to fix the title of this thread? :)
  http://forums.worldofwarcraft.com/thread.aspx?fn=wow-interface-customization&t=238150&p=#post289857
Poster: slouken at 1/3/2006 9:58:52 PM PST
Subject: Re: Patch 1.9 Changes - Concise List
   By the way, this might help some addon authors who are trying to deal with the scale changes in 1.9:

First, the way scale is handled changed internally from being an override to properly propogating down the frame hierarchy.

This means that if A was a parent of B, and A set it's scale to 0.5, then B would also have a scale of 0.5, and then if B set a scale of 0.75, it would have a new scale of 0.75. With the new changes, it would have a new scale of 0.375.

This was intended to make it possible for frames to set their relative scale regardless of how the entire UI is scaled. However, this wasn't effectively communicated in the patch notes and was understated in the changes thread.

The new behavior is this:
Frame:SetScale() sets the frame's own scale relative to it's parent frame.
Frame:GetScale() gets the frame's own scale relative to it's parent frame.
Frame:GetEffectiveScale() gets the frame's total effective scale.

Here are two functions (untested) that may help ease the pain:

function GetEffectiveScale(frame)
return frame:GetEffectiveScale()
end
function SetEffectiveScale(frame, scale)
frame.scale = scale; -- Saved in case it needs to be re-calculated when the parent's scale changes.
local parent = frame:GetParent();
if ( parent ) then
scale = scale / GetEffectiveScale(parent);
end
frame:SetScale(scale);
end

Then, replace all occurrences of frame:GetScale() with GetEffectiveScale(frame) and all occurrences of frame:SetScale(scale) with SetEffectiveScale(frame, scale)

[ post edited by slouken ]

  http://forums.worldofwarcraft.com/thread.aspx?fn=wow-interface-customization&t=238150&p=#post290761
Poster: slouken at 1/11/2006 9:15:05 AM PST
Subject: Re: Upcoming 1.9 Changes - Concise List
  

Q u o t e:
Please slouken, can we get this information back?


The information wasn't actually there, it had been removed several patches ago, but the UI code hadn't been updated (resulting in broken who UI)

Anyway, no, it's not coming back.
  http://forums.worldofwarcraft.com/thread.aspx?fn=wow-interface-customization&t=238150&p=#post299127
Poster: slouken at 1/25/2006 7:47:35 PM PST
Subject: Re: Patch 1.9 (thro 1.9.2) Changes - Concise
  

Q u o t e:
Slouken,

Any plans to fix the Unit Dropdown menus to account for the increased Inspect range? The Inspect menu option is still greying out using the old range check.


I think actually that's the correct range. That you can inspect from a longer range is simply a bug that we haven't gotten around to fixing.
  http://forums.worldofwarcraft.com/thread.aspx?fn=wow-interface-customization&t=238150&p=#post308888
Poster: slouken at 1/25/2006 7:47:35 PM PST
Subject: Re: Patch 1.9 (thro 1.9.2) Changes - Concise *edited post*
  

Q u o t e:
Slouken,

Any plans to fix the Unit Dropdown menus to account for the increased Inspect range? The Inspect menu option is still greying out using the old range check.


I think actually that's the correct range. That you can inspect from a longer range is simply a bug that we haven't gotten around to fixing.

Edit: I'll double-check if I have time though.

[ post edited by slouken ]

  http://forums.worldofwarcraft.com/thread.aspx?fn=wow-interface-customization&t=238150&p=#post308888
Poster: slouken at 1/25/2006 7:47:35 PM PST
Subject: Re: Patch 1.9 (thro 1.9.2) Changes - Concise *edited post*
  

Q u o t e:
Slouken,

Any plans to fix the Unit Dropdown menus to account for the increased Inspect range? The Inspect menu option is still greying out using the old range check.


I think actually that's the correct range. That you can inspect from a longer range is simply a bug that we haven't gotten around to fixing.

[ post edited by slouken ]

  http://forums.worldofwarcraft.com/thread.aspx?fn=wow-interface-customization&t=238150&p=#post308888

View all recent official Blue Posts

WoW Blue Tracker: Archiving World of Warcraft Blue Posts
since March 2005
Home | RSS | News | Contact
Recent | Search | Archive | CS Posts
 

Why Ads?