025

BazMap

025 (2026-05-04)

Full Changelog Previous Releases

• v025: detail-mode layout, BlizzMove fix, drag stability
  Three related fixes plus a refactor.
  1. Quest detail view is now a third remembered layout. Clicking a
     tracked quest in the objective tracker opens the map with quest
     details attached - a hybrid state distinct from pure map mode and
     pure quest log mode. The addon's two-mode model collapsed it into
     one of the others and applied the wrong size, leaving a big empty
     region in the frame. Probing DetailsFrame.questID via the public
     QuestMapFrame_GetDetailQuestID helper gives a clean three-mode
     answer; new defaults detailScale and detailDraggable; new settings
     page section; reset slash command clears detailPosition too.
  2. Hooks on QuestMapFrame_ShowQuestDetails / _CloseQuestDetails /
     _ReturnFromQuestDetails plus a HandleModeChange wrapper that only
     fires save+apply on a real mode change. Stops the cascade-induced
     redundant ApplyAll calls that fired three times per click-tracked-
     quest path and could persist intermediate-state saves.
  3. BlizzMove disable rewritten. Old code called BlizzMove:DisableFrame
     with the wrong addon namespace ("Blizzard_WorldMap" - silently a
     no-op since BlizzMove registers WorldMapFrame under its own self.name)
     and no persistence. New code uses BlizzMoveAPI:UnregisterFrame with
     permanent=true, fired from file scope + BlizzMove ADDON_LOADED + InitMap
     so it wins whichever load-order race happens. Persists across /reload.
  4. isDragging flag set by titleBar OnMouseDown/OnMouseUp; ApplyAll
     short-circuits while it's true so Blizzard's SynchronizeDisplayState
     refresh, OnSizeChanged, or any stale handler can't teleport the
     frame mid-drag. WorldMapFrame doesn't expose IsMovingOrSizing on
     its class, hence the manual marker.
     User guide rewritten to acknowledge three layouts. Note: cross-mode
     position memory is best-effort - Blizzard's WorldMapFrame mixin runs
     its own internal layout passes (SetWidth in SetQuestLogPanelShown,
     Maximize/Minimize, SynchronizeDisplayState) on every transition that
     no addon can fully override. Same wall Leatrix Maps hits.