In the Rise of Azshara content update, we’ve developed several user interface changes that we’d like to call your attention to.

Accessibility Features

First, we’ve added several slash commands intended to provide more options for vision-impaired players. Some of these commands will allow the player to enter and leave voice channels without having to physically click the voice button in the channels list:

Enter voice channel for your guild: /voice guild

Enter voice channel for the officer channel for your guild: /voice officer

Enter general channel for the given community: /voice

Enter a particular channel for the given community: /voice

Leave the current voice channel: /voice leave

We’ve also added some other new commands are intended to facilitate creating and joining communities and Battlenet clubs:

Open the Add Community Dialog with the invitation link edit box selected. Just paste in the link and hit : /community join

Open the create wow character community dialog with the Name edit box selected. Type in a name, then , then enter a short name, and hit to finalize the creation: /community create wow

Open the create Battlenet club dialog with the Name edit box selected. Type in a name, then optionally hit and enter a short name, and hit to finalize the creation: /community create battlenet

Frame Anchoring

We added new restricted frames system that affects frame anchoring:

Frames that are anchored to a restricted frame can only have their other anchors set to frames within that same anchor hierarchy

Added new API in the Line API: Line:ClearAllPoints();

This will clear the anchors on a line and must be called to clear the restricted flag off of the frame.

New restricted frames include:

Nameplates



The following APIs are now blocked from being called on restricted frames:

GetCenter()

GetLeft()

GetRight()

GetTop()

GetBottom()

GetRect()

GetScaledRect()

GetBoundsRect()

Tooltip Add Texture

We added the ability to have multiple customizable textures per line.

Usage:

Tooltip:AddTexture(fileDataID/”filename” [,minx, maxx, miny, maxy])

– will be deprecated soon

or

Tooltip:AddTexture(fileDataID/”filename” [,TooltipTextureInfo])

– new way

TooltipTextureInfo is a table that describes how to apply the texture:

{

width = 12, – can be 0 to use actual texture width

height = 12, – can be 0 to use actual texture size

anchor = Enum.TooltipTextureAnchor.Left,

region = Enum.TooltipTextureRelativeRegion.LeftLine,

verticalOffset = 0,

margin = { left = 8, right = 8, top = 0, bottom = 0 }, – empty space around the texture, can be negative

texCoords = { left = 0, right = 1, top = 0, bottom = 1 },

vertexColor = { r = 1, g = 1, b = 1, a = 1 },

}

The values above are the internal defaults. The table may be partially filled out and any unspecified settings will be used at their default values.

Added optional left and top padding.

Usage:

Tooltip:SetPadding(right, bottom, [left, top])

Report System

In this content update, we’re going to put a restriction on a couple of functions. The C_ReportSystem.InitiateReportPlayer and C_ReportSystem.SendReportPlayer functions are no longer allowed to be called by addons. Addons can now open the normal ‘Player Reporting’ dialog by calling the new function C_ReportSystem.OpenReportPlayerDialog. The player will be required to interact with that dialog to actually send the report.

Texture Access

One more notable change: Accessing textures outside of the …/Interface directory no longer support paths, and now requires a file data ID. In order to support this change, we’re going through our Set Texture functions to make sure file data IDs are supported everywhere.

Please feel free to give us your feedback or questions on any of the above here in this thread.

Thank you!