🚀 go-pugleaf

RetroBBS NetNews Server

Inspired by RockSolid Light RIP Retro Guy

Article View: alt.games.warcraft
Article #352127

lock waypoints in Tomtom?

#352127
From: Peter T.
Date: Thu, 22 Dec 2016 21:24
9 lines
1655 bytes
Back in MoP I was able to lock waypoints in Tomtom so they didnt 
disappear when I passed through them.  Now I cant find that option 
anywhere.  Help?

I have asked the same question at Tomtom's curseforge site and 
Blizzard's forum and those still remain unanswered..

-- 
Peter T.
Technical Details
Message-ID: <o3hgbj$16ek$1@gioia.aioe.org>
Path: mbox-mo1.pugleaf.net!m27ni6365qtf.1!nntp.google.com!peer02.iad!feed-me.highwinds-media.com!peer02.am4!peer.am4.highwinds-media.com!news.highwinds-media.com!news.unit0.net!news.mixmin.net!aioe.org!.POSTED!not-for-mail

Show Full Headers
Complete Article Headers
X-Received: by 10.107.195.204 with SMTP id t195mr3122404iof.79.1482441911626;        Thu, 22 Dec 2016 13:25:11 -0800 (PST)
X-BeenThere: alt.games.warcraft@googlegroups.com
Received: by 10.157.13.228 with SMTP id 91ls23595055ots.42.gmail; Thu, 22 Dec 2016 13:25:10 -0800 (PST)
X-Received: by 10.200.52.137 with SMTP id w9mr2809736qtb.70.1482441910739;        Thu, 22 Dec 2016 13:25:10 -0800 (PST)
Path: mbox-mo1.pugleaf.net!m27ni6365qtf.1!nntp.google.com!peer02.iad!feed-me.highwinds-media.com!peer02.am4!peer.am4.highwinds-media.com!news.highwinds-media.com!news.unit0.net!news.mixmin.net!aioe.org!.POSTED!not-for-mail
From: "Peter T." <pinoc10@hotmail.cum>
Newsgroups: alt.games.warcraft
Subject: lock waypoints in Tomtom?
Date: Thu, 22 Dec 2016 22:24:51 +0100
Organization: Aioe.org NNTP Server
Lines: 9
Message-ID: <o3hgbj$16ek$1@gioia.aioe.org>
NNTP-Posting-Host: pvUGIXhczZBaNE1+jDNPLA.user.gioia.aioe.org
Mime-Version: 1.0
X-Complaints-To: ab...@aioe.org
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.5.1
X-Mozilla-News-Host: news://nntp.aioe.org:119
X-Notice: Filtered by postfilter v. 0.8.2
X-Antivirus-Status: Clean
X-Antivirus: avast! (VPS 161222-4, 22-12-2016), Outbound message
X-Received-Body-CRC: 338317478
X-Received-Bytes: 1205
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit