You must login to post a comment. Don't have an account? Register to get one!

• 

  • Reply
  • #6

  Archarodim Feb 26, 2011 at 18:23 UTC - 0 likes

  @acapela: I've done some testing, HHTD is able to add its cross but there is a lot of issues when using Aloft.
  Many LibNamePlate callbacks are broken:

  - GetNameplateByGUID() seems to not work for enemies' nameplates
  - event: LibNameplate_NewNameplate fires twice for each new name plate (breaking uniqueness detection)

  Thanks for your testing, I've fixed 1. I'll make some tests about 2.

• 

  • Reply
  • #4

  Archarodim Feb 25, 2011 at 05:23 UTC - 0 likes

  well you should not use killthehealer since it will prevent LibNamePlate to work.
  Try without to see if it changes something.
  From its description, LibNamePlate is meant to be compatible with Aloft.

• 

  • Reply
  • #3

  Codex Feb 25, 2011 at 01:29 UTC - 0 likes

  Im getting this from your call to libnameplate 1x LibNameplate-1.0-27:286: attempt to index field 'isOnScreen' (a nil value) LibNameplate-1.0-27:830: in function <...ve-To-Die\Libs\LibNameplate-1.0\LibNameplate-1.0.lua:822>

  was running it with both Aloft, Icile and KillTheHealer!

  Last edited Feb 25, 2011 by Codex
• 

  • Reply
  • #2

  Archarodim Feb 24, 2011 at 23:17 UTC - 0 likes

  @acapela: HHTD uses the LibNameplate-1.0 library and it adds a texture to plates

  What you're looking for is in the NPH:AddCrossToPlate() function in NamePlateHooker.lua

  make sure to grab the current alpha/beta version, there was a lot of changes since last release

• 

  • Reply
  • #1

  acapela Feb 24, 2011 at 21:26 UTC - 0 likes

  update: got a chance to play with this, and it looks like it works with Aloft to me (your addon version 1.80_beta_1, my current Aloft development based on Aloft-4.3.3-2081). the Curse screen shot shows different artwork, but the current code seems to use the Blizzard "healer" role LFG artwork, which is what i am seeing.

  a few issues:

  1) as i was fiddling with options, i did experience a LUA error, line 331 of Core.lua, no value to "format". i addressed this by having UpdateHealThreshold() return zero (0) on line 480 of Core.lua.

  2) as fiddled with options, i was able to "break" something. it seemed to have to do with the "Healer Forget Timer". once a healer had been timed out, new heal activity did not result in new visible artwork on still-visiblenameplates. i had to hide and show nameplates again (via keybinding) to get the artwork to show up. i expect that leaving nameplate range and returning would have the same effect.

  3) very rarely, layering of your artwork seems to alter as i show/hide nameplates (via keybinding). usually it worked great (your art above nameplate bar art but below text/etc). very rarely, your art would appear below nameplate bar art. this could easily be a Blizzard glitch. it might/not be amenable to frame-delay.

  -

  i am the current Aloft author/maintainer. i just tweaked "KillTheHealer" (http://wow.curse.com/downloads/wow-addons/details/killthehealer.aspx) to work with Aloft.

  problems with "KillTheHealer":

  1) it added a texture region to the base nameplate frame (which apparetly alters the manifest of texture regions enough to "break" Aloft). solution: create a new frame (child of the nameplate assembly) and add the texture region to that. this might not ultimately have been necessary, but...

  2) it was hooking the "OnShow" script for the base nameplate frame (without saving the "old" handler and invoking it as part of the new handler). solution: hook the "OnShow" script handler for the new frame mentioned in 1) above.

  i will take a look at this addon as well, when i get a chance. i want Aloft to be able to coexist with all of these things.

  Last edited Feb 25, 2011 by acapela