Oh right, wanted to post pics: http://i27.tinypic.com/adnbtc.jpg Being in Terokkar, the waypoint to The Rokk in Shattrath only shows the distance, but no arrow.
getting two error constantly..(updated to latest even with wowaceupd)
[2008/06/27 13:31:10-1666-x1]: Cartographer_Waypoints-2.0\Waypoints.lua:507: attempt to index field 'db' (a nil value)
LibRock-1.0-3317 (LibRock-1.0):2594: in function <Interface\AddOns\LibRock-1.0\LibRock-1.0.lua:2557>
LibRock-1.0-3317 (LibRock-1.0):2715: in function <Interface\AddOns\LibRock-1.0\LibRock-1.0.lua:2710>
<in C code>: in function `LoadAddOn'
Interface\FrameXML\UIParent.lua:908: in function `UIParentLoadAddOn':
Interface\FrameXML\UIParent.lua:234: in function `CombatLog_LoadUI':
Interface\FrameXML\UIParent.lua:327: in function <Interface\FrameXML\UIParent.lua:312>:
<in C code>: in function `UIParent_OnEvent'
<string>:"*:OnEvent":1: in function <[string "*:OnEvent"]:1>
---
[2008/06/27 13:31:17-1666-x1585]: Cartographer_Waypoints-2.0\Waypoints.lua:1091: attempt to index field 'tex' (a nil value)
LibRockTimer-1.0-1118 (LibRockTimer-1.0):289: in function <...terface\AddOns\LibRockTimer-1.0\LibRockTimer-1.0.lua:227>
Getting similar error as Tommysp. I updated all my addons today:
2008/07/01 21:20:48-1-x1]: Cartographer_Waypoints-2.0\Waypoints.lua:507: attempt to index field 'db' (a nil value)
LibRock-1.0-3317 (LibRock-1.0):2594: in function <Interface\AddOns\LibRock-1.0\LibRock-1.0.lua:2557>
LibRock-1.0-3317 (LibRock-1.0):2715: in function <Interface\AddOns\LibRock-1.0\LibRock-1.0.lua:2710>
<in C code>: in function `LoadAddOn'
Interface\FrameXML\UIParent.lua:908: in function `UIParentLoadAddOn':
Interface\FrameXML\UIParent.lua:234: in function `CombatLog_LoadUI':
Interface\FrameXML\UIParent.lua:327: in function `UIParent_OnEvent':
<string>:"*:OnEvent":1: in function <[string "*:OnEvent"]:1>
[2008/07/01 21:20:56-1-x351]: Cartographer_Waypoints-2.0\Waypoints.lua:1091: attempt to index field 'tex' (a nil value)
LibRockTimer-1.0-1118 (LibRockTimer-1.0):289: in function <...terface\AddOns\LibRockTimer-1.0\LibRockTimer-1.0.lua:227>
---
With patch 2.4.3 the waypoint on screen text is showing up with an extra %d listed:
This is due to LibAbacus I believe. I've seen a few other modules modify their handling of the DAYS_ABBR arguments, maybe LibAbacus needs modified as well. *shrugs*.
Yes, I have noticed that it works well still with questhelper but I have to disable waypoint and then enable it again to show the waypoint. I don't know if there is a way around this.
After an arrow shown, the left time text contains a "%d" which should not be displayed.
My OS: English Vista
My Region: China Mainland
My WoW: Taiwan Version (zhTW)
I found the %d between number and unit text in every unit. e.g. "12 %d 秒", "5 %d 分鐘".
I read the source code and have no idea about the reason. But I found a way to pass the bug. Just add these line after line 88 in LibAbacus-3.0.lua (r79915):
Oh I did =) But -technically- moving the folder shouldn't make any difference, and if it did, I'm missing something in my 'folder location' code that tries to take account of whether the folder is within the main cart folder or not =)
I know this is a really old post, but does this mean I can put all the Cartographer_* folders inside the top-level Cartographer?
Date: 2008-11-08 14:54:24
ID: 16
Error occured in: Global
Count: 1
Message: ...nterface\AddOns\Cartographer_Waypoints\Waypoints.lua line 1191:
attempt to index field 'tex' (a nil value)
Debug:
[C]: ?
...nterface\AddOns\Cartographer_Waypoints\Waypoints.lua:1191: object_method()
...Ons\FuBar\libs\LibRockTimer-1.0\LibRockTimer-1.0.lua:289:
...Ons\FuBar\libs\LibRockTimer-1.0\LibRockTimer-1.0.lua:227
Cartographer r2290 (v2.3.6a) (all its modules enabled), disembedded updated libs (except for embedded LibGuild-1.0 & LibGuildPositions-1.0), USEng client/server, WoW 3.0.3 live. Lightheaded, TourGuide or any other mod that can use the Waypoints arrow are not enabled.
Start with a new saved variables. Log on, make sure Waypoints is enabled in the Cartographer options panel accessed through the map frame. Create a new waypoint on a zone map (in Northrend, Outlands or wherever) via the default CTRL-click drop down menu. The waypoint appears in the upper right corner of the UI/screen. Click to drag it to a better position (such as the middle/top of screen). As soon as you release the click, the waypoint shoots down to the far bottom left corner of the screen. Which makes it pretty much unusable (at least compared with TomTom); the text below the arrow is no longer visible.
Try to move it again back to the center/middle of the UI. Again, as soon as you release the click, it spontaneously shoots back down to the identical bottom left corner of the UI as before.
This behavior is continually reproducible. Relog after this occurs, the arrow is stuck in the bottom corner and continually goes back there after releasing the mouse click after dragging it to a preferred position. It happens if you reset the saved variables. And it happens if you go into the Cartographer.lua saved variables file and change "["waypointX"] =" & "["waypointY"] =" under the "["Waypoints"] = {" header to a preferred position before logging on. It doesn't seem to read those saved variables pixel settings.
This was similarly somewhat of a problem for quite a period of time long ago as well in WoW 2.4 and prior. Move the arrow by click-dragging it and it "shot" around a bit after you released the mouse key. But...it did not "shoot" down to the bottom left of the screen, it moved on its own a substantially fewer number of pixels around. The current revisions post-WoW 3.0 have amplified the problem.
The Waypoints arrow is apparently not setting, reading or storing its pixel position properly in either memory or its saved variables.
This is the only Cart module with an issue here. TomTom does not have this issue. Neither do virtually any other movable-frame mods I've tried. Except one: the ancient ShowMe (http://www.wowinterface.com/downloads/info7457-ShowMe.html; it still works in the current WoW). The frame for that doesn't maintain its set pixel position through relogs. It does not, however, shoot randomly to the bottom left corner of the UI as Cartographer's Waypoint does; it remains where you move it to until you relog.
This thread isn't used anymore. The only people that still try (and fail) to maintain Cartographer2 aren't really part of the WowAce community and don't frequent the forums afaik. Everybody else that has worked on Cartographer2 has abandoned it.
This thread isn't used anymore. The only people that still try (and fail) to maintain Cartographer2 aren't really part of the WowAce community and don't frequent the forums afaik. Everybody else that has worked on Cartographer2 has abandoned it.
Yah, I know. I'd abandon it too by now if Astrolabe didn't multiply its CPU usage with (for instance) each and every TomTom waypoint put on a map ;).
The current Cartographer-replacement mods that use Astrolabe are great. Wish that library was more efficient than it is, though.
I really hope that Cartographer_Waypoints is going to be maintained for a while. I am a user of the Zygor InGame 01-80 Power Levelling Guide which makes heavy usage of the arrow of Cartographer_Waypoints of course. I am currently using the latest version of both, Cartographer r2290 (v2.3.6a), and Zygor Guide from December 19th, 2008. Cartographer comes bundled with the commerical guide from the Zygor homepage.
It does work but currently one needs to do the following EVERYTIME when starting a new WoW session, which is pretty annoying:
(this is a quote from http://www.zygorguides.com/members/support.php)
1) go into cartographer and if waypoints are enabled, disable them.
2) reload your ui
3) go back into cartographer waypoints and re-enable them
4) open up zygor guide and under the map addon options change it to 'none'
5) now change it back to cartographer2
By following these 5 steps (a kind of reset procedure) at the beginning of a new WoW session I am able to get the arrow (which then works perfectly) of Cartographer_Waypoints.
Zygor's Guide works with TomTom, so go install that instead. In fact, I believe Zygor's Guide comes packaged with TomTom now, and no longer uses Cartographer_Waypoints.
Rollback Post to RevisionRollBack
To post a comment, please login or register a new account.
http://i27.tinypic.com/adnbtc.jpg Being in Terokkar, the waypoint to The Rokk in Shattrath only shows the distance, but no arrow.
[arrow image]
1. distance
2. Waypoint
3. time
is it possible making each off them or all (1,2,3) optional hidden?
[2008/06/27 13:31:10-1666-x1]: Cartographer_Waypoints-2.0\Waypoints.lua:507: attempt to index field 'db' (a nil value)
LibRock-1.0-3317 (LibRock-1.0):2594: in function <Interface\AddOns\LibRock-1.0\LibRock-1.0.lua:2557>
LibRock-1.0-3317 (LibRock-1.0):2715: in function <Interface\AddOns\LibRock-1.0\LibRock-1.0.lua:2710>
<in C code>: in function `LoadAddOn'
Interface\FrameXML\UIParent.lua:908: in function `UIParentLoadAddOn':
Interface\FrameXML\UIParent.lua:234: in function `CombatLog_LoadUI':
Interface\FrameXML\UIParent.lua:327: in function <Interface\FrameXML\UIParent.lua:312>:
<in C code>: in function `UIParent_OnEvent'
<string>:"*:OnEvent":1: in function <[string "*:OnEvent"]:1>
---
[2008/06/27 13:31:17-1666-x1585]: Cartographer_Waypoints-2.0\Waypoints.lua:1091: attempt to index field 'tex' (a nil value)
LibRockTimer-1.0-1118 (LibRockTimer-1.0):289: in function <...terface\AddOns\LibRockTimer-1.0\LibRockTimer-1.0.lua:227>
This is due to LibAbacus I believe. I've seen a few other modules modify their handling of the DAYS_ABBR arguments, maybe LibAbacus needs modified as well. *shrugs*.
Date: 2008-08-02 10:10:44
ID: 77
Error occured in: Global
Count: 1
Message: ...ns\Cartographer\Cartographer_Waypoints\Waypoints.lua line 991:
attempt to index field 'db' (a nil value)
Debug:
[C]: ?
...ns\Cartographer\Cartographer_Waypoints\Waypoints.lua:991: AddWaypoint()
...ns\Cartographer\Cartographer_Waypoints\Waypoints.lua:970: AddLHWaypoint()
LightHeaded\LightHeaded.lua:604: OnHyperlinkClick()
LightHeaded\LightHeaded.lua:1066:
LightHeaded\LightHeaded.lua:1066
AddOns:
ArkInventory, v2.27
AtlasLoot, vAtlasLoot Enhanced v4.06.02
AucAdvanced, v5.0.PRE.3117
AucFilterBasic, v5.0.PRE.3117 (BillyGoat)
AucScanData, v1.0
AucStatClassic, v5.0.PRE.3117 (BillyGoat)
AucStatPurchased, v5.0.PRE.3117 (BillyGoat)
AucStatSimple, v5.0.PRE.3117 (BillyGoat)
AucStatStdDev, v5.0.PRE.3117 (BillyGoat)
Auctioneer, v5.0.PRE.3117
AutoBar, v2.04.02.56 beta
Bartender3, v3.1.2 r78566
BeanCounter, v5.0.PRE.3117 (BillyGoat)
Cartographer, vr79583
CartographerTrainers, v1.0
CartographerVendors, v1.0
CartographerFishing, v1.0
CartographerIcons, v1.0
CartographerIconsCtMapModPack, v1.0
CartographerIconsGathererPack, v1.0
CartographerIconsMetaMapPack, v1.0
CartographerImport, v1.0
CartographerNoteshare, v1.0
CartographerNoteTarget, v0.3
Clique, v96
CTCore, v2.401 (CTMod 2.0)
CTMailMod, v3.02 (CTMod 2.0)
cyCircled, v0.5
ElkBuffBars, v2.1
Enchantrix, v5.0.PRE.3117
EnchantrixBarker, v5.0.PRE.3117 (BillyGoat)
EnhTooltip, v5.0.PRE.3117
EquipCompare, v2.12
ErrorMonster, v2
Examiner, v08.03.26
FishingAce, v0.4.2k
GFWAdSpace, v2.4
GFWGemologist, v2.4
GFWReagentCost, v2.4
FuBarBagFu, v2.0
FuBarChatAlertsFu, v0.95
FuBarClockFu, v3.0
FuBarCraftTimersFu
FuBarDurabilityFu, v2.0
FuBarFriendsFu, v2.4
FuBarFuXPFu, v3
FuBarGuildFu, v2.4
FuBarLocationFu, v3.0
FuBarMailFu, v2.0
FuBarMoneyFu, v20400-1
FuBarPerformanceFu, v2.0
FuBarRegenFu, v2.1.0
FuBarSkillsPlusFu, v2.4.6
FuBarTopScoreFu, v2.0
FuBar, v60201
FuTextures, v2.0
Gatherer, v3.1.2
Grid, v76416
GridAlert, v72732
GridSideIndicators, v0.4
GridStatusHealingReduced, v1.1
GridStatusHots, v2.3b
GridStatusMissingBuffs, v2.2.0.00
GridStatusMTs, v1.0
GridStatusThreat, v2.0
ImprovedCamera, v2.0.1
Informant, v5.0.PRE.3117
ItemSync, vr55400
AbacusLib
LibAbacus30
Ace2
Ace3
AnchorsAway, v1.0
Babble22, v2.2.$Revision: 66632 $
LibBabbleBoss30
LibBabbleClass30
LibBabbleCreatureType30
LibBabbleFaction30
LibBabbleInventory30
LibBabbleSpell30
LibBabbleZone30
LibBanzai20, v2.0
CandyBar
CrayonLib
LibCrayon30
Deformat, v1.0 $Revision: 3817 $
DewdropLib
LibDogTag30, v1.0
LibDogTagUnit30, v1.0
FuBarPlugin20, v2.0 $Revision: 66634 $
LibFuBarPlugin30, v2.0 $Revision: 44269 $
LibGraph20, v2.0
GratuityLib, vr$Revision: 66041 $
LibGratuity30, vr$Revision: 41183 $
LibGUIDRegistry01
LibGuildPositions10, v1.0
LibHealComm30
JostleLib
LibJostle30
LibKeyBound10
LibKeyBoundExtra10
LibStub
Metrognome, v2.0
PaintChipsLib
LibPeriodicTable31, v3.1
LibResComm10
LibRock10
LibRockComm10
LibRockConfig10
LibRockConsole10
LibRockDB10
LibRockEvent10
LibRockHook10
LibRockLocale10
LibRockModuleCore10
LibRockTimer10
RosterLib, v2.1
SharedMediaLib, v1.0
LibSharedMedia20
LibSharedMedia30, v3.0
SinkLib
LibSink20
SpecialEventsEmbed
LibStickyFrames20
TabletLib
LibTalentQuery10, v$Rev: 66356 $
Talismonger30
Threat20
TouristLib
LibTourist30
Waterfall10
WhoLib, v1.0
WindowLib
LightHeaded, v241
LightHeadedDataB, v241
MirageUIClearFont2FontPack, v20400.1
MirageUIClearFont2, v20400.1 Mirage UI
MirageUICore, v20400.01
MirageUIcyCircled, v20400.1
MirageUIXPBar, v20400.1
MirageUISunnViewportArtPack, v20400.1
MobInfo2, v3.61
MonkeyBuddy, v2.7
MonkeyLibrary
MonkeyQuest, v2.7
MonkeyQuestLog, v0.5.1
NaturCombat, v9.0BETA2
Omen, vOmen r79486 / Threat-2.0 r79668
OmniCC, v2.0.8
oRA2, v2.0.$Revision: 70972 $
Outfitter, v4.1.1
PallyPower, v2.01.00
PreformAVEnabler
QuestAnnouncer, v0.5
Recount, v79538
sct, v6.2
sctd, v3.1
simpleMinimap, v20100-6
Skillet, v1.10-61015
SpamMeNot, v2.4
sRaidFrames
Steamroller
Stubby, v52
SunnArt, v2.12
Swatter, v5.0.PRE.3117
TipBuddy, v2.40
TrinketMenu
VoidReaverAlarm
WIM, v2.4.15
WOWEconPriceMod
XPerlArcaneBar
XPerlParty
XPerlPartyPet
XPerlPlayerBuffs
XPerlPlayer
XPerlPlayerPet
XPerlRaidFrames
XPerlTarget
XPerlTargetTarget
XPerl, v2.4.0b
XLootGroup, v0.5
XLootMaster, v0.7
XLootMonitor, v0.7
XLoot, v0.9
DBMAPI
Any ideas what it could cause it?
I'm using version 20400 and I found a bug.
After an arrow shown, the left time text contains a "%d" which should not be displayed.
My OS: English Vista
My Region: China Mainland
My WoW: Taiwan Version (zhTW)
I found the %d between number and unit text in every unit. e.g. "12 %d 秒", "5 %d 分鐘".
I read the source code and have no idea about the reason. But I found a way to pass the bug. Just add these line after line 88 in LibAbacus-3.0.lua (r79915):
I know this is a really old post, but does this mean I can put all the Cartographer_* folders inside the top-level Cartographer?
Date: 2008-11-08 14:54:24
ID: 16
Error occured in: Global
Count: 1
Message: ...nterface\AddOns\Cartographer_Waypoints\Waypoints.lua line 1191:
attempt to index field 'tex' (a nil value)
Debug:
[C]: ?
...nterface\AddOns\Cartographer_Waypoints\Waypoints.lua:1191: object_method()
...Ons\FuBar\libs\LibRockTimer-1.0\LibRockTimer-1.0.lua:289:
...Ons\FuBar\libs\LibRockTimer-1.0\LibRockTimer-1.0.lua:227
Cartographer_Waypoints-2.0\Waypoints.lua:993: attempt to index field 'db' (a nil value)
Start with a new saved variables. Log on, make sure Waypoints is enabled in the Cartographer options panel accessed through the map frame. Create a new waypoint on a zone map (in Northrend, Outlands or wherever) via the default CTRL-click drop down menu. The waypoint appears in the upper right corner of the UI/screen. Click to drag it to a better position (such as the middle/top of screen). As soon as you release the click, the waypoint shoots down to the far bottom left corner of the screen. Which makes it pretty much unusable (at least compared with TomTom); the text below the arrow is no longer visible.
Try to move it again back to the center/middle of the UI. Again, as soon as you release the click, it spontaneously shoots back down to the identical bottom left corner of the UI as before.
This behavior is continually reproducible. Relog after this occurs, the arrow is stuck in the bottom corner and continually goes back there after releasing the mouse click after dragging it to a preferred position. It happens if you reset the saved variables. And it happens if you go into the Cartographer.lua saved variables file and change "["waypointX"] =" & "["waypointY"] =" under the "["Waypoints"] = {" header to a preferred position before logging on. It doesn't seem to read those saved variables pixel settings.
This was similarly somewhat of a problem for quite a period of time long ago as well in WoW 2.4 and prior. Move the arrow by click-dragging it and it "shot" around a bit after you released the mouse key. But...it did not "shoot" down to the bottom left of the screen, it moved on its own a substantially fewer number of pixels around. The current revisions post-WoW 3.0 have amplified the problem.
The Waypoints arrow is apparently not setting, reading or storing its pixel position properly in either memory or its saved variables.
This is the only Cart module with an issue here. TomTom does not have this issue. Neither do virtually any other movable-frame mods I've tried. Except one: the ancient ShowMe (http://www.wowinterface.com/downloads/info7457-ShowMe.html; it still works in the current WoW). The frame for that doesn't maintain its set pixel position through relogs. It does not, however, shoot randomly to the bottom left corner of the UI as Cartographer's Waypoint does; it remains where you move it to until you relog.
Yah, I know. I'd abandon it too by now if Astrolabe didn't multiply its CPU usage with (for instance) each and every TomTom waypoint put on a map ;).
The current Cartographer-replacement mods that use Astrolabe are great. Wish that library was more efficient than it is, though.
It does work but currently one needs to do the following EVERYTIME when starting a new WoW session, which is pretty annoying:
(this is a quote from http://www.zygorguides.com/members/support.php)
1) go into cartographer and if waypoints are enabled, disable them.
2) reload your ui
3) go back into cartographer waypoints and re-enable them
4) open up zygor guide and under the map addon options change it to 'none'
5) now change it back to cartographer2
By following these 5 steps (a kind of reset procedure) at the beginning of a new WoW session I am able to get the arrow (which then works perfectly) of Cartographer_Waypoints.
The Zygor Guide DOES NOT support Cartographer 3 :-( , see the quote here of the plans of the Zygor development team:
http://www.zygorguides.com/forum/showthread.php?t=861