Dungeon map stays small in the middle after going from the quest log (L) to the maximized map (M) inside a dungeon
Maintainers usually reply within 1 day
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 72/100
Research direction
Start with Map/Window.lua, especially FillScreen around lines 79–87, then follow Refit() to ScrollContainer:OnCanvasSizeChanged. Check how maximizing or minimizing and showing or hiding the quest log updates the Blizzard dungeon map canvas. Done means the map art fills the maximized window after the described L-to-M sequence; verify behavior without affecting the stitched world map.
Written by the indexing model from the issue text.
Description
Steps
- Inside a dungeon, press L (quest log, windowed map).
- Press M (maximized map).
The dungeon map art keeps the small window's size and sits in the middle of the big window.
Closing and reopening the map shows it at the right size.
It is Blizzard's own map for that dungeon, not the stitched world map.
Cause (read from the code, not confirmed in game)
Map/Window.lua FillScreen (lines 79-87) calls Refit() only when it actually changes the
frame width:
if math.abs(map:GetWidth() - w) < 1 then return end
map:SetWidth(w)
Refit()
When the width is already the full width, Refit (ScrollContainer:OnCanvasSizeChanged)
is not called, so the canvas keeps the old fit.
Workaround I use
Calling WorldMapFrame.ScrollContainer:OnCanvasSizeChanged() after Maximize/Minimize and
after the quest log shows/hides, when the map is not the stitched one.
Environment
- WoW Forever (Interface 16001), Korean client (koKR)
- OpenMap v0.8.9
- Other addons: Attune, Auctionator, ForeverDungeonJournal, ForeverPowerBars, RogueEnergyCombo
- Tested with OpenMap disabled: the message in issue 1 stopped appearing (short test, a few minutes)
- Dominant language
- Lua
- Stars
- 20
- Forks
- 6
- Avg merge
- 23h 27m
- Merged PRs (30d)
- 45
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from openmap-world/openmap
-
forever from-game
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
openmap-world/openmap#399 ·
Maintainers usually reply within 1 day
-
forever from-game
Difficulty 2/5 1-3 hours Newbie friendliness 61/100
openmap-world/openmap#386 ·
Maintainers usually reply within 1 day
-
forever from-game
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
openmap-world/openmap#333 ·
Maintainers usually reply within 1 day
-
Quest log covers the mapPossibly taken A pull request linked to this issue is open or already merged. Openforever from-game
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
openmap-world/openmap#327 · 4 comments ·
Maintainers usually reply within 1 day
-
enhancement forever from-game
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
openmap-world/openmap#117 ·
Maintainers usually reply within 1 day
All issues in openmap-world/openmap
Similar issues
-
bug discord guide:04-redridge-mountains locale:enUS triage v4.1.1
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
Maintainers usually reply within 1 day
-
Data Correction Forever
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
bug question widgets
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
GrayWolf64/imgui-lua#48 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
Maintainers usually reply within 1 day