WoWInterface

WoWInterface (https://www.wowinterface.com/forums/index.php)
-   nUI: Bug Reports (https://www.wowinterface.com/forums/forumdisplay.php?f=90)
-   -   Cant move the objective tracker anymore. (https://www.wowinterface.com/forums/showthread.php?t=48258)

Aelendil 09-28-13 12:15 PM
Cant move the objective tracker anymore.
 
For some reason with /nui movers I can't move the objective tracker anymore it doesn't show as moveable.

grhuff07 09-28-13 12:37 PM
I noticed this in the last version as well (.37), so I don't think it was introduced in .38.

Xrystal 09-28-13 01:07 PM
what about in the versions before 5.4 came out. The blizzard objective frame has had some code changes in 5.4 although I've not looked into it myself as I use my own objective frame. But the one in nUI is not a customized one so its possible that blizz have overridden nUI's moving code with its own.

grhuff07 09-28-13 02:32 PM
Quote:
Originally Posted by Xrystal (Post 285247)
what about in the versions before 5.4 came out. The blizzard objective frame has had some code changes in 5.4 although I've not looked into it myself as I use my own objective frame. But the one in nUI is not a customized one so its possible that blizz have overridden nUI's moving code with its own.
I've only recently started playing WoW and my first version of nUI was .37 so I won't be much help here.

rj_killeen 09-28-13 03:39 PM
I have the same issue, and it has only re-set the Objectives position with this newest download.

Previous updates did not re-set the Objectives.

Xrystal 09-28-13 06:17 PM
Not quite sure what happened with the file as there are no comments in the update to say it had been changed but if you look at the following block of code and find the similar block in the nUI_Movers.lua file in the plugin folder and change it to the block I show afterward it should allow you to use the mover system again ... and hopefully Scott will spot this post :D

Lua Code:
  1. {
  2.     frameName = "QuestWatchFrame",
  3.     labelText = "Watched Quests",
  4.     parent = nil,
  5.     addOn = nil,
  6.     exclusionFrames = 
  7.     {
  8.         [1] = "WatchFrame"
  9.     },
  10.     requiredFrames = nil,
  11.     defaultPosition = 
  12.     {
  13.         anchorPt = "TOPLEFT", 
  14.         relativeTo = "nUI_TopBars", 
  15.         relativePt = "BOTTOMLEFT", 
  16.         xOfs = 50, 
  17.         yOds = 120
  18.     },
  19. },

Lua Code:
  1. {
  2. --  frameName = "QuestWatchFrame",
  3.     frameName = "WatchFrame",
  4.     labelText = "Watched Quests",
  5.     parent = nil,
  6.     addOn = nil,
  7. --  exclusionFrames = 
  8. --  {
  9. --      [1] = "WatchFrame"
  10. --  },
  11.     requiredFrames = nil,
  12.     defaultPosition = 
  13.     {
  14.         anchorPt = "TOPLEFT", 
  15.         relativeTo = "nUI_TopBars", 
  16.         relativePt = "BOTTOMLEFT", 
  17.         xOfs = 50, 
  18.         yOds = 120
  19.     },
  20. },

spiel2001 09-28-13 06:37 PM
Ah... yeah... my bad. I was doing some testing trying to sort out some taint stuff and forgot to fix it.

grhuff07 09-28-13 07:12 PM
Quote:
Originally Posted by grhuff07 (Post 285250)
I've only recently started playing WoW and my first version of nUI was .37 so I won't be much help here.
I just realized I wrote these comments in the wrong thread. I meant for them to be in the bug report for the combat log movement issue. I noticed that issue with nUI 5.07.37 so it wasn't introduced in 5.07.38. Sorry for the confusion there.

Xrystal 09-29-13 01:33 AM
Scott, also, dugi noticed that around line 792 there is also a WatchFrame move code line that has been commented out. This stops the actual watchframe itself from moving.

The two changes together will both add the watchframe to the mover system and move the actual watchframe when you mover the mover for it.

spiel2001 09-30-13 05:07 AM
Roger that -- If I can get the time, I'll try to get a fix out tonight.


All times are GMT -6. The time now is 12:15 AM.

vBulletin © 2024, Jelsoft Enterprises Ltd
© 2004 - 2022 MMOUI