Poster: Sedge at 7/1/2006 1:42:55 PM PDT
Subject: slouken: SetCursor() custom textures issues |
| |
There are two issues I've found with using custom textures for the cursor.
The first issue is that it appears we can only use blp files (and not tga files). This isn't a big issue as it's not hard to convert tgas into blps.
The second issue is that if the cursor system does not know about the cursor texture already, the cursor cannot be displayed while in hardware cursor mode. For example this texture does not work in hardware cursor mode, but it works otherwise:
/script SetCursor("Interface\\ChatFrame\\UI-ChatIcon-ScrollDown-Up")
This texture works in either mode, as it is a normal cursor texture (one the cursor system already knows about):
/script SetCursor("Interface\\Cursor\\PickLock")
This is only an issue with direct3d, as in opengl mode hardware cursor appears to be permanently disabled.
Is this second issue fixable? Should we just work around it? Is it specific to hardware configuration in some way?[ post edited by Sedge ]
moo?
|
| | http://forums.worldofwarcraft.com/thread.aspx?fn=wow-interface-customization&t=407142&p=#post407142 |
| |
Poster: slouken at 7/6/2006 10:20:47 AM PDT
Subject: Re: slouken: SetCursor() custom textures issues |
| |
Q u o t e:
The first issue is that it appears we can only use blp files (and not tga files). This isn't a big issue as it's not hard to convert tgas into blps.
That's correct.
Q u o t e:
The second issue is that if the cursor system does not know about the cursor texture already, the cursor cannot be displayed while in hardware cursor mode.
The blp files must be uncompressed, otherwise the alpha channel loses some precision and the hardware cursur (which uses overlay 1-bit transparency) will think the cursor is transparent.
|
| | http://forums.worldofwarcraft.com/thread.aspx?fn=wow-interface-customization&t=407142&p=#post409817 |
