HandyNotes: TravelGuide

HandyNotes: TravelGuide

2M Downloads

Error handler.lua [Retail]

Hollicsh opened this issue ยท 6 comments

commented

27x ...rfaceHandyNotes_TravelGuide\core\handler.lua:83: attempt to index local 'poi' (a nil value)
[string "@HandyNotes_TravelGuide\core\handler.lua"]:83: in function <...rfaceHandyNotes_TravelGuide\core\handler.lua:78>
[string "=[C]"]: ?

Locals:
self = WorldMapFrame {
0 =
ShouldPanOnClick = defined @Blizzard_MapCanvas\Blizzard_MapCanvas.lua:683
GetMinZoomViewRect = defined @Blizzard_MapCanvas\Blizzard_MapCanvas.lua:703
PanTo = defined @Blizzard_MapCanvas\Blizzard_MapCanvas.lua:650
HandleUserActionOpenSelf = defined @FrameXML\QuestLogOwnerMixin.lua:91
AreDetailLayersLoaded = defined @Blizzard_MapCanvas\Blizzard_MapCanvas.lua:450
RemovePin = defined @Blizzard_MapCanvas\Blizzard_MapCanvas.lua:215
OnCanvasScaleChanged = defined @Blizzard_MapCanvas\Blizzard_MapCanvas.lua:590
RemoveGlobalPinMouseActionHandler = defined @Blizzard_MapCanvas\Blizzard_MapCanvas.lua:837
OnQuestLogOpen = defined @FrameXML\QuestLogOwnerMixin.lua:219
CalculatePinNudging = defined @Blizzard_MapCanvas\Blizzard_MapCanvas.lua:324
OnCanvasSizeChanged = defined @Blizzard_MapCanvas\Blizzard_MapCanvas.lua:606
ApplyPinPosition = defined @Blizzard_MapCanvas\Blizzard_MapCanvas.lua:510
SetAreaTriggerIntersectsCallback = defined @Blizzard_MapCanvas\Blizzard_MapCanvas.lua:270
ShouldZoomInstantly = defined @Blizzard_MapCanvas\Blizzard_MapCanvas.lua:691
HandleUserActionToggleQuestLog = defined @FrameXML\QuestLogOwnerMixin.lua:44
NavBar = {
}
pinNudgingDirty = false
SetGlobalPinScale = defined =[C]:-1
RefreshDebugAreaTriggers = defined @Blizzard_MapCanvas\Blizzard_MapCanvas.lua:398
SetShouldNavigateOnClick = defined @Blizzard_MapCanvas\Blizzard_MapCanvas.lua:671
NavigateToParentMap = defined @Blizzard_MapCanvas\Blizzard_MapCanvas.lua:783
SetDebugAreaTriggersEnabled = defined @Blizzard_MapCanvas\Blizzard_MapCanvas.lua:422
SetFocusedQuestID = defined @Blizzard_WorldMap\Blizzard_WorldMap.lua:420
UnregisterEvents = defined @SharedXML\CallbackRegistry.lua:140
EvaluateLockReasons = defined @Blizzard_MapCanvas\Blizzard_MapCanvas.lua:753
GetGlobalPinScale = defined @Blizzard_MapCanvas\Blizzard_MapCanvas.lua:891
SetDisplayState = defined @FrameXML\QuestLogOwnerMixin.lua:99
TitleCanvasSpacerFrame = {
}
OnLoad = defined @Blizzard_WorldMap\Blizzard_WorldMap.lua:82
RemoveDataProviderEvent = defined @Blizzard_MapCanvas\Blizzard_MapCanvas.lua:128
GetNumActivePinsByTemplate = defined @Blizzard_MapCanvas\Blizzard_MapCanvas.lua:231
SetPinTemplateType = defined @Blizzard_MapCanvas\Blizzard_MapCanvas.lua:204
AddOverlayFrames = defined @Blizzard_WorldMap\Blizzard_WorldMap.lua:217
SetAreaTriggerEnclosedCallback = defined @Blizzard_MapCanvas\Blizzard_MapCanvas.lua:265
IsCanvasMouseFocus = defined @Blizzard_MapCanvas\Blizzard_MapCanvas.lua:739
GetCanvasScale = defined @Blizzard_MapCanvas\Blizzard_MapCanvas.lua:610
SetGlobalAlpha = defined @Blizzard_MapCanvas\Blizzard_MapCanvas.lua:911
RemoveDataProvider = defined @Blizzard_MapCanvas\Blizzard_MapCanvas.lua:117
minimizedHeight = 534
lockReasons =

{
}
GetScaleForMinZoom = defined @Blizzard_MapCanvas\Blizzard_MapCanvas.lua:711
NavigateToCursor = defined @Blizzard_MapCanvas\Blizzard_MapCanvas.lua:790
RemoveCursorHandler = defined @Blizzard_MapCanvas\Blizzard_MapCanvas.lua:861
AdjustDetailLayerAlpha = <functio

commented

Thank you for reporting this error.
My last commit should fix this error, but I'm a little curious what you've done when this error occurred.

commented

To be honest, I don't understand how it happened ..
Most likely I opened the map and this error immediately got out.

commented

Do you know which map you opened ?

commented

Most likely I opened the map in Oribos.
I can't be sure, but I think it is.
This error popped up quite unexpectedly.
According to my observations, it was after I opened the map (M).

commented

To be honest, I was surprised myself when I saw this error.

commented

I tried to reproduce the error in Oribos with the version before the fix and I didn't got it, but the new version v2.10.1 should have fixed it. I'll close this issue now, but feel free to open it again if it should happen again with the new version.