TomTom - WoW AddOns - CurseForge

TomTom is your personal navigation assistant in World of Warcraft. This addon is very simple, but provides a nice set of functionality. Thanks to Esamynn for Astrolabe, which does the bulk of the work in this addon.

Bugs and Support (PLEASE READ)
Unfortunately I have been forced to disable user comments on Curse.com. For some absurd reason the site has stopped sending me emails when you guys post a new comment, making me completely unable to provide support via this means. I am still happy to provide assistance, both on Curseforge and Wowinterface:

http://wow.curseforge.com/addons/tomtom/tickets
http://www.wowinterface.com/downloads/fileinfo.php?id=7032

TomTom offers the following major features:

Set waypoints via command, or by clicking on the world map
A draggable coordinate display with customizable accuracy. This frame can be hidden or locked.
Player and cursor coordinates on the World Map (these can be hidden)
A floating "crazy-taxi" style arrow that points you to your destination
Displaying the "crazy-taxi" arrow or coordinate block in compatible LDB displays, such as NinjaPanel
Show a waypoint that points you towards your corpse for easy recovery
Can set waypoints by clicking on quest objective POIs on the World Map and watch frame.

Please also check out LightHeaded

Slash Commands:
/tomtom - Opens configuration GUI

In addition you can use the /way command to add and reset waypoints. In order to overcome conflicts with the Cartographer /way command, you can also use /tway to access TomTom's waypoint command. The following slash commands are available:

Slash Command	Description
/way 14.78 23.9	Add a new waypoint at 14.78, 23.90
/way Nagrand 45 50	Add a new waypoint in Nagrand at 45, 50
/way 14.78 23.90 This is a waypoint!	Add a new waypoint with a description
/way reset all	Remove ALL current waypoints
/way reset Nagrand	Remove all waypoints in Nagrand
/wayb or /wayback	Sets a waypoint at the current location
/cway or /closestway	Set the crazy arrow to the closest waypoint

TomTom has been designed to publish the Crazy-Arrow and Coordinate Block as LDB feeds, allowing them to be displayed in compatible display addons. I've written a very simple, easy-to-configure panel that is capable of displaying these called NinjaPanel.

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

50 comments
1
2
3
4
5
Next →

- Reply
- #50
Pakka Jun 29, 2011 at 14:07 UTC - 0 likes
@Cladhaire: Go

Seems complicated... yes, I already reported it to the authors of atlasloot and they promised to further investigate the issue.
- Reply
- #49
Cladhaire Jun 29, 2011 at 13:53 UTC - 0 likes
Possibly because we are including a newer version of the library than they are. Possibly because there is some other form of interaction going on. In short, I'm not sure what to tell you, but there's not a single call to TomTom anywhere in your stack trace, whereas there are calls to AtlasLoot. Please contact them, and they can contact me with any further issues.
- Reply
- #48
Pakka Jun 29, 2011 at 13:50 UTC - 0 likes
@Cladhaire: Go

Unfortunately I have 0/525 LUA editing. But, allow me to ask: if it is an issue with atlas or atlasloot and the way they use AceDB, why does it only generate errors when TomTom and Archy are used too? Atlas and Atlasloot both work fine with my lvl2 bank char, cause he's NOT using TomTom or Archy - no error code generated. Don't understand this.

(made updates to my post below, error codes)

Last edited Jun 29, 2011 by Pakka
- Reply
- #47
Cladhaire Jun 29, 2011 at 13:36 UTC - 0 likes
You'll need to talk to the Atlas author, this is just an issue with AceDB or the way he's accessing it. Not much I can do on my end, he's just using an embedded library =)
- Reply
- #46
Pakka Jun 29, 2011 at 13:00 UTC - 0 likes
Using Atlas 1.20, Atlasloot v6.04.01 and TomTom 1.4.0

Opening atlas via hitting the atlas minimap button results in bugsack catching this (memory usage of TomTom rises from 1.2 MB to about 55 MB):

1x TomTom-v40100-1.4.0\libs\AceDB-3.0\AceDB-3.0-21.lua:94: stack overflow TomTom-v40100-1.4.0\libs\AceDB-3.0\AceDB-3.0-21.lua:94: in function <TomTom\libs\AceDB-3.0\AceDB-3.0.lua:91> TomTom-v40100-1.4.0\libs\AceDB-3.0\AceDB-3.0-21.lua:123: in function <TomTom\libs\AceDB-3.0\AceDB-3.0.lua:91> TomTom-v40100-1.4.0\libs\AceDB-3.0\AceDB-3.0-21.lua:123: in function <TomTom\libs\AceDB-3.0\AceDB-3.0.lua:91> TomTom-v40100-1.4.0\libs\AceDB-3.0\AceDB-3.0-21.lua:123: in function <TomTom\libs\AceDB-3.0\AceDB-3.0.lua:91> TomTom-v40100-1.4.0\libs\AceDB-3.0\AceDB-3.0-21.lua:123: in function <TomTom\libs\AceDB-3.0\AceDB-3.0.lua:91> TomTom-v40100-1.4.0\libs\AceDB-3.0\AceDB-3.0-21.lua:123: in function <TomTom\libs\AceDB-3.0\AceDB-3.0.lua:91> TomTom-v40100-1.4.0\libs\AceDB-3.0\AceDB-3.0-21.lua:123: in function <TomTom\libs\AceDB-3.0\AceDB-3.0.lua:91> TomTom-v40100-1.4.0\libs\AceDB-3.0\AceDB-3.0-21.lua:123: in function <TomTom\libs\AceDB-3.0\AceDB-3.0.lua:91> TomTom-v40100-1.4.0\libs\AceDB-3.0\AceDB-3.0-21.lua:123: in function <TomTom\libs\AceDB-3.0\AceDB-3.0.lua:91> TomTom-v40100-1.4.0\libs\AceDB-3.0\AceDB-3.0-21.lua:123: in function <TomTom\libs\AceDB-3.0\AceDB-3.0.lua:91> TomTom-v40100-1.4.0\libs\AceDB-3.0\AceDB-3.0-21.lua:123: in function <TomTom\libs\AceDB-3.0\AceDB-3.0.lua:91> TomTom-v40100-1.4.0\libs\AceDB-3.0\AceDB-3.0-21.lua:123: in function <TomTom\libs\AceDB-3.0\AceDB-3.0.lua:91> Archy-1.8.3\Libs\AceAddon-3.0\AceAddon-3.0-10.lua:628: in function <Archy\Libs\AceAddon-3.0\AceAddon-3.0.lua:621> <in C code> AtlasLoot_Loader\AtlasLoot_Loader-v6.04.01.lua:94: in function "LoadModule" AtlasLoot_Loader\AtlasLoot_Loader-v6.04.01.lua:76: in function <AtlasLoot_Loader\AtlasLoot_Loader.lua:73> <in C code> <in C code> FrameXML\UIParent.lua:1936: in function "ShowUIPanel" Atlas\Core\Atlas-1.20.0.lua:812: in function "Atlas_Toggle" Atlas-1.20.0\Core\AtlasButton.lua:32: in function "AtlasButton_OnClick" <string>:"*:OnClick":1: in function <string>:"*:OnClick":1

Locals: nil ---------------------
- update* disabling TomTom results in the same error, but with Archy - so I get the feeling it has to do something with the AceDB lib maybe?
1x Archy-1.8.3\Libs\AceDB-3.0\AceDB-3.0-21.lua:94: stack overflow Archy-1.8.3\Libs\AceDB-3.0\AceDB-3.0-21.lua:94: in function <Archy\Libs\AceDB-3.0\AceDB-3.0.lua:91> Archy-1.8.3\Libs\AceDB-3.0\AceDB-3.0-21.lua:123: in function <Archy\Libs\AceDB-3.0\AceDB-3.0.lua:91> Archy-1.8.3\Libs\AceDB-3.0\AceDB-3.0-21.lua:123: in function <Archy\Libs\AceDB-3.0\AceDB-3.0.lua:91> Archy-1.8.3\Libs\AceDB-3.0\AceDB-3.0-21.lua:123: in function <Archy\Libs\AceDB-3.0\AceDB-3.0.lua:91> Archy-1.8.3\Libs\AceDB-3.0\AceDB-3.0-21.lua:123: in function <Archy\Libs\AceDB-3.0\AceDB-3.0.lua:91> Archy-1.8.3\Libs\AceDB-3.0\AceDB-3.0-21.lua:123: in function <Archy\Libs\AceDB-3.0\AceDB-3.0.lua:91> Archy-1.8.3\Libs\AceDB-3.0\AceDB-3.0-21.lua:123: in function <Archy\Libs\AceDB-3.0\AceDB-3.0.lua:91> Archy-1.8.3\Libs\AceDB-3.0\AceDB-3.0-21.lua:123: in function <Archy\Libs\AceDB-3.0\AceDB-3.0.lua:91> Archy-1.8.3\Libs\AceDB-3.0\AceDB-3.0-21.lua:123: in function <Archy\Libs\AceDB-3.0\AceDB-3.0.lua:91> Archy-1.8.3\Libs\AceDB-3.0\AceDB-3.0-21.lua:123: in function <Archy\Libs\AceDB-3.0\AceDB-3.0.lua:91> Archy-1.8.3\Libs\AceDB-3.0\AceDB-3.0-21.lua:123: in function <Archy\Libs\AceDB-3.0\AceDB-3.0.lua:91> Archy-1.8.3\Libs\AceDB-3.0\AceDB-3.0-21.lua:123: in function <Archy\Libs\AceDB-3.0\AceDB-3.0.lua:91> Archy-1.8.3\Libs\AceAddon-3.0\AceAddon-3.0-10.lua:514: in function "InitializeAddon" Archy-1.8.3\Libs\AceAddon-3.0\AceAddon-3.0-10.lua:628: in function <Archy\Libs\AceAddon-3.0\AceAddon-3.0.lua:621> <in C code> AtlasLoot_Loader\AtlasLoot_Loader-v6.04.01.lua:94: in function "LoadModule" AtlasLoot_Loader-v6.04.01\MiniMap-LDB.lua:21: in function "OnClick" Archy-1.8.3\Libs\LibDBIcon-1.0\LibDBIcon-1.0-19.lua:122: in function <Archy\Libs\LibDBIcon-1.0\LibDBIcon-1.0.lua:122>

Locals: nil -----------------
- update* Further testing, with my warlock: after disabling TomTom and Archy, no further mod is specifically named in the error code that bugsack catches, instead the AceDB-3.0 itself. Btw, getting the error and then trying to logout or /reload ui results in crashing to desktop with the wow client closed. Unfortunately I have 0/525 LUA editing, so I really don't know what exactly is causing this and who is "responsible" for a fix.
1x Libs\AceDB-3.0\AceDB-3.0-21.lua:94: stack overflow Libs\AceDB-3.0\AceDB-3.0-21.lua:94: in function <Libs\AceDB-3.0\AceDB-3.0.lua:91> Libs\AceDB-3.0\AceDB-3.0-21.lua:123: in function <Libs\AceDB-3.0\AceDB-3.0.lua:91> Libs\AceDB-3.0\AceDB-3.0-21.lua:123: in function <Libs\AceDB-3.0\AceDB-3.0.lua:91> Libs\AceDB-3.0\AceDB-3.0-21.lua:123: in function <Libs\AceDB-3.0\AceDB-3.0.lua:91> Libs\AceDB-3.0\AceDB-3.0-21.lua:123: in function <Libs\AceDB-3.0\AceDB-3.0.lua:91> Libs\AceDB-3.0\AceDB-3.0-21.lua:123: in function <Libs\AceDB-3.0\AceDB-3.0.lua:91> Libs\AceDB-3.0\AceDB-3.0-21.lua:123: in function <Libs\AceDB-3.0\AceDB-3.0.lua:91> Libs\AceDB-3.0\AceDB-3.0-21.lua:123: in function <Libs\AceDB-3.0\AceDB-3.0.lua:91> Libs\AceDB-3.0\AceDB-3.0-21.lua:123: in function <Libs\AceDB-3.0\AceDB-3.0.lua:91> Libs\AceDB-3.0\AceDB-3.0-21.lua:123: in function <Libs\AceDB-3.0\AceDB-3.0.lua:91> Libs\AceDB-3.0\AceDB-3.0-21.lua:123: in function <Libs\AceDB-3.0\AceDB-3.0.lua:91> Libs\AceDB-3.0\AceDB-3.0-21.lua:123: in function <Libs\AceDB-3.0\AceDB-3.0.lua:91> AtlasLoot_Loader-v6.04.01\Libs\AceAddon-3.0\AceAddon-3.0-10.lua:514: in function "InitializeAddon" ...\AtlasLoot_Loader\Libs\AceAddon-3.0\AceAddon-3.0-10.lua:628: in function <...\AtlasLoot_Loader\Libs\AceAddon-3.0\AceAddon-3.0.lua:621> <in C code> AtlasLoot_Loader\AtlasLoot_Loader-v6.04.01.lua:94: in function "LoadModule" AtlasLoot_Loader-v6.04.01\MiniMap-LDB.lua:21: in function "OnClick" Libs\LibDBIcon-1.0\LibDBIcon-1.0-19.lua:122: in function <Libs\LibDBIcon-1.0\LibDBIcon-1.0.lua:122>

Locals: nil
Last edited Jun 29, 2011 by Pakka
- Reply
- #45
Cladhaire May 08, 2011 at 09:13 UTC - 0 likes
Nope, but thanks for the report. TomTom only appears in the error log because Archy is using the AceEvent that's embedded in TomTom. Let Archy know and I'm sure they'll be able to sort it out!
- Reply
- #44
Pakka May 08, 2011 at 09:10 UTC - 0 likes
Don't know if this has anything to do with TomTom, for I have 0/525 in Lua editing, but TomTom appears in the error log, so...

1x AceLocale-3.0: Archy: Missing entry for 'Unknown': Archy-1.7b8 bugfix12\Archy.lua:2498: in function <Archy\Archy.lua:2473> Archy-1.7b8 bugfix12\Archy.lua:2521: in function <Archy\Archy.lua:2517> Archy-1.7b8 bugfix12\Archy.lua:3677: in function `?' CallbackHandler-1.0-6:147: in function <...Tom\libs\CallbackHandler-1.0\CallbackHandler-1.0.lua:147> <string>:"safecall Dispatcher[1]":4: in function <[string "safecall Dispatcher[1]"]:4> <in C code>: ? <string>:"safecall Dispatcher[1]":13: in function `?' CallbackHandler-1.0-6:92: in function `Fire' AceEvent-3.0-3 (TomTom):120: in function <...ace\AddOns\TomTom\libs\AceEvent-3.0\AceEvent-3.0.lua:119>

-

Last edited May 08, 2011 by Pakka
- Reply
- #43
Cladhaire Apr 24, 2011 at 13:14 UTC - 0 likes
No need to post in both places. Please check my response on the ticket.
- Reply
- #42
Pakka Apr 24, 2011 at 02:41 UTC - 0 likes
I confirm the error reported by evlyxx, ticket ID 20, about low fps and stutter after death and release in Stonecore dungeon, Deepholm.

Every time I die in the Stonecore dungeon and release my spirit, the game starts to stutter and lag extremely. Re-logging fixes it until the next death/ release. Took me a while to figure this out, but disabling TomTom solves the problem. It's also the reason why it only affects my warlock, because my hunter doesn't use TomTom. However, I don't know if it would affect my hunter too when using TomTom, didn't test this yet. Version was 1.2.2, but I see evlyxx uses current 1.2.6 and still has the issue.
- Reply
- #41
Museraen331 Feb 05, 2011 at 15:26 UTC - 0 likes
I went and checkd to see if I had the latest version of Questpointer installed and it turned out I didn't and he made the changes I am talking about. Sorry for that. He now has TomTom's crazyarrow point to the nearest POI of the quest whereas that wasn't an option before. QP is a lightweight quest addon that works great especially now. It also seems that he is a big fan of your addon so here is a cop/paste of the info he provides.

QuestPointer puts the quest POI icons from the world map onto your minimap.

It’ll integrate with TomTom’s crazyarrow, if you have it installed. Click the broker plugin or type “/qp closest” to have the crazyarrow point to the current closest quest POI.

You can choose to:

•Auto-track the closest POI in TomTom •Only show icons for quests you’re watching •Make icons on the edge of the minimap become arrows to make it more obvious that they’re far away •Change the icon scale

Again, I'm sorry for the miss information and hope I didn't inconvenience you to much.