Hello, find this bug with Carto r28363 on a FR client:
Hope this can help :)
[2007/02/18 09:25:00-438-x1]: ...ns\Cartographer\Cartographer_Waypoints\Waypoints.lua:202: Cannot find a library instance of Abacus-2.0.:
Ace2\AceLibrary\AceLibrary.lua:422: in function `AceLibrary'
...ns\Cartographer\Cartographer_Waypoints\Waypoints.lua:202: in main chunk:
---
if self.OnMap and db and db[self.Zone] and db[self.Zone][self.POIID] then
db[self.Zone][self.POIID] = nil
end
if #Cartographer_Waypoints.Queue > 1 then
for i,v in pairs(db[self.Zone]) do
if i == Cartographer_Waypoints.Queue[2].POIID then
v.focus = true
end
end
end
end
I'm standing in netherstorm and cannot clear waypoints anymore.
Ok, you may remember the problem with the not existing arrow.
I messed now around today to find the problem ... i didnt found it yet, but i thought to tell you the steps i have done:
1. I deactivated all addons, except of Cartographer and its modules. ---> no arrow
2. I did a back-up, deleted wtf and and the AddOn folder, downloaded manually cartographer, let the lod run and started the game again. ---> no arrow
3. With this new installation, i first messed around with the graphik setting of WoW. I set everything on "on" and on high quality. ---> no arrow
With these 3 points, i came to the conclusion, that the error cant be caused by something else than cartographer or a library of it.
So i began to take a look into your source-code.
Well, i am not a "pro" with programming, but if i am not wrong this is the code for calling the "arrow-frame":
(Line 350) local function createWaypointFrame()
path = debugstack(1, 1, 0)
if path:find("grapher\\") then
(Line 353) path = "Interface\\AddOns\\Cartographer\\Cartographer_Waypoints\\Artwork\\Arrow"
elseif path:find("grapher_Waypoints\\") then
(Line 355) path = "Interface\\AddOns\\Cartographer_Waypoints\\Artwork\\Arrow"
else
error("Cannot determine path of artwork")
end
So, if i understood it right, the program takes first a look for the "packed-cartographer" ... the path would be then "Line 353".
If i am using the lod version ... he should use "Line 355".
Well, i am using the lod version, so i messed around with "Line 355". This was getting so far, that i changed the code to this:
local function createWaypointFrame()
path = debugstack(1, 1, 0)
if path:find("Cartographer\\") then
path = "Interface\\AddOns\\Cartographer\\Cartographer_Waypoints\\Artwork\\Arrow"
elseif path:find("Cartographer_Waypoints\\") then
path = "Interface\\AddOns\\Cartographer_Waypoints\\nonsense\\Arrow"
else
error("Cannot determine path of artwork")
end
Well, the folder "nonsense" is not existing, so normally the addon should tell me now: "Cannot determine path of artwork"
I restarted WoW ... made a note in the area i was ... set a waypoint .. i got the distance, the name of the waypoint but i got no arrow and no error-message.
May be my knowledge of programming is much more worse than i thought, or the addon isnt calling the frame at all.
I dont have an idea to go this way ... like i said: my knowledge isnt very good ;)
Well, unfortunatly at this point, a guildmate came online.
Just to remeber:
We have 2 PC's/accounts in the guild on which its working, and 2 PC's/accounts on which it isnt working.
Due to the fact, that it is working on a few pc's my thoughts about the frames above, might be totally wrong. So i thought: what are the differences ?
Well, this is i found out:
1. playing with german-client, no ELP installed ---> no arrow
2. playing with german-client, no ELP installed ---> no arrow
3. playing with german-client, english-ELP installed but not used ---> HAS arrow
4. german-client installed, playing with english-ELP ---> HAS arrow
Is it may be pure chance, that the arrow isnt shown on pcs/accounts where the english-ELP isnt installed ?
Well, it seems not logical, because there is someone playing with the german client, but the english-ELP is installed in the backround.
I am aware that a lot of ace-addons problems on my side, are caused by the localization, because a lot of source code is different to the other languages.
rightio, fixed the duplicate waypoint issue, with 28505. Mattftw, I'm really not sure why you're not getting a corpsepoint, unless you're in a battleground, from which I've heard has some issues which is why I turned it off for there.
Lightning, could you try with the Cart_Waypoint -inside- the Cart folder (eg packed) just to see if it's the path that's causing issues?
Would it be reasonable to exclude instances when doing z-Xxx searches? I can't think of why I would search for a waypoint in an instance from outside. Obviously, doesn't mean there isn't a reason, just that I can't seem to think of one. :)
For example, I made a note at the flight path in Hellfire Penninsula, and I like to fly straight there from Shattrath. So, I use /way z-hell flight, but that tells me there's nothing in Hellfire Ramparts, which is true. I either end up flying there "by hand", or typing out z-"Hellfire P" (quotes are working great now btw, thanks :).
Ok, i downloaded it again, and keept it "packed" ... i didnt changed the folders only modified the Waypoints.lua.
I changed the lines to:
local function createWaypointFrame()
path = debugstack(1, 1, 0)
if path:find("grapher\\") then
path = "Interface\\AddOns\\Cartographer\\Cartographer_Waypoints\\nonsense\\Arrow"
elseif path:find("grapher_Waypoints\\") then
path = "Interface\\AddOns\\Cartographer_Waypoints\\nonsense\\Arrow"
else
error("Cannot determine path of artwork")
end
Started the "fresh" WoW ... and everything was the same.
I set a note in the area i was, marked it as a waypoint, and got the distance and the name of the point.
No error message.
Edited because I'm a bit slow and didn't read Lightning's posts closer hehe. Anyways I'm having the same problem as him. No arrow shows on death or any other time. It's a fresh install with no saved variables already present.
Also wouldn't WoW return an error if it was looking for the texture in the wrong place? For example "no such texture exists" yada yada.
...
Also wouldn't WoW return an error if it was looking for the texture in the wrong place? For example "no such texture exists" yada yada.
That was the idea in messing up the path .. there doesnt come any error. So in my opinion, the addon isnt trying to call the texture properly.
And now we come to the great question:
It does it, when i am dead ... but not with a "normal" waypoint e.g. in Shattrath. What is the difference in the code ?
I don't know either, I wish I knew how to get you more information. I've tried a freshly svn'd version as the only addon with a new WTF folder, I've tried dling the latest prezipped file, all with the same results. I can manualy add a waypoint, but the corpse waypoint just doesnt work.
><
Lightning, you get the waypoint arrow when you're dead, but not normally? That's kinda bizarre... There -is- no difference in code for the arrow... although... I am suspecting it's to do with the zone names in English and German. Let me do some more tracking down tonight, to see that I'm keeping a common flow on the usage...
><
Lightning, you get the waypoint arrow when you're dead, but not normally? That's kinda bizarre...
You are totally right. And even more bizarre then i see, that its working perfectly well if you have the ELP installed. You dont have to use it ... you just need the installation in the backround.
Tbh, that scares me -.-
All works fine on my system. I gave my interface folder to a friend.
He has also the problem that no arrow appears after death (yes, the option is turned on). the only difference between his and my wow is I have the enGB client, he has the german client withouth any language packs.
Maytrix, it's an option you'll have to set in the menu, as some people were complaining about it turning up automatically and being insulted by the death messages =P
Sharky: It looks like it's a german localisation issue. Trying to track it down a bit =)
Rollback Post to RevisionRollBack
To post a comment, please login or register a new account.
Hope this can help :)
local db = Waypoint.MapDB
if self.OnMap and db and db[self.Zone] and db[self.Zone][self.POIID] then
db[self.Zone][self.POIID] = nil
end
if #Cartographer_Waypoints.Queue > 1 then
for i,v in pairs(db[self.Zone]) do
if i == Cartographer_Waypoints.Queue[2].POIID then
v.focus = true
end
end
end
end
I'm standing in netherstorm and cannot clear waypoints anymore.
self.Zone == "Limbo"
db[self.Zone] == nil
so I get lua errors
build 28278
asked a guard for the bank.
/waypoint bank
deleted waypoint, worked fine
/waypoint bank
/waypoint bank
(entered twice to get a queue)
when tried to delete Waypoint.prototype:RemoveFromMap() blew up because db[self.Zone] == nil
it says: true
I messed now around today to find the problem ... i didnt found it yet, but i thought to tell you the steps i have done:
1. I deactivated all addons, except of Cartographer and its modules. ---> no arrow
2. I did a back-up, deleted wtf and and the AddOn folder, downloaded manually cartographer, let the lod run and started the game again. ---> no arrow
3. With this new installation, i first messed around with the graphik setting of WoW. I set everything on "on" and on high quality. ---> no arrow
With these 3 points, i came to the conclusion, that the error cant be caused by something else than cartographer or a library of it.
So i began to take a look into your source-code.
Well, i am not a "pro" with programming, but if i am not wrong this is the code for calling the "arrow-frame":
So, if i understood it right, the program takes first a look for the "packed-cartographer" ... the path would be then "Line 353".
If i am using the lod version ... he should use "Line 355".
Well, i am using the lod version, so i messed around with "Line 355". This was getting so far, that i changed the code to this:
Well, the folder "nonsense" is not existing, so normally the addon should tell me now: "Cannot determine path of artwork"
I restarted WoW ... made a note in the area i was ... set a waypoint .. i got the distance, the name of the waypoint but i got no arrow and no error-message.
May be my knowledge of programming is much more worse than i thought, or the addon isnt calling the frame at all.
I dont have an idea to go this way ... like i said: my knowledge isnt very good ;)
Well, unfortunatly at this point, a guildmate came online.
Just to remeber:
We have 2 PC's/accounts in the guild on which its working, and 2 PC's/accounts on which it isnt working.
Due to the fact, that it is working on a few pc's my thoughts about the frames above, might be totally wrong. So i thought: what are the differences ?
Well, this is i found out:
1. playing with german-client, no ELP installed ---> no arrow
2. playing with german-client, no ELP installed ---> no arrow
3. playing with german-client, english-ELP installed but not used ---> HAS arrow
4. german-client installed, playing with english-ELP ---> HAS arrow
Is it may be pure chance, that the arrow isnt shown on pcs/accounts where the english-ELP isnt installed ?
Well, it seems not logical, because there is someone playing with the german client, but the english-ELP is installed in the backround.
I am aware that a lot of ace-addons problems on my side, are caused by the localization, because a lot of source code is different to the other languages.
Any ideas ?
Lightning, could you try with the Cart_Waypoint -inside- the Cart folder (eg packed) just to see if it's the path that's causing issues?
Would it be reasonable to exclude instances when doing z-Xxx searches? I can't think of why I would search for a waypoint in an instance from outside. Obviously, doesn't mean there isn't a reason, just that I can't seem to think of one. :)
For example, I made a note at the flight path in Hellfire Penninsula, and I like to fly straight there from Shattrath. So, I use /way z-hell flight, but that tells me there's nothing in Hellfire Ramparts, which is true. I either end up flying there "by hand", or typing out z-"Hellfire P" (quotes are working great now btw, thanks :).
I changed the lines to:
Started the "fresh" WoW ... and everything was the same.
I set a note in the area i was, marked it as a waypoint, and got the distance and the name of the point.
No error message.
Also wouldn't WoW return an error if it was looking for the texture in the wrong place? For example "no such texture exists" yada yada.
That was the idea in messing up the path .. there doesnt come any error. So in my opinion, the addon isnt trying to call the texture properly.
And now we come to the great question:
It does it, when i am dead ... but not with a "normal" waypoint e.g. in Shattrath. What is the difference in the code ?
Lightning, you get the waypoint arrow when you're dead, but not normally? That's kinda bizarre... There -is- no difference in code for the arrow... although... I am suspecting it's to do with the zone names in English and German. Let me do some more tracking down tonight, to see that I'm keeping a common flow on the usage...
You are totally right. And even more bizarre then i see, that its working perfectly well if you have the ELP installed. You dont have to use it ... you just need the installation in the backround.
Tbh, that scares me -.-
He has also the problem that no arrow appears after death (yes, the option is turned on). the only difference between his and my wow is I have the enGB client, he has the german client withouth any language packs.
Sharky: It looks like it's a german localisation issue. Trying to track it down a bit =)