unify(gui): Move game window files to Core - #3197
Conversation
PR Summary by QodoCentralize shared game-window implementation in Core
AI Description
Diagram
High-Level Assessment
Files changed (10)
|
Code Review by Qodo🐞 Bugs (0) 📘 Rule violations (0) 📎 Requirement gaps (0)
Great, no issues found!Qodo reviewed your code and found no material issues that require reviewTip of the day💡 Did you know, you can hide the parts of a finding you never read, like the evidence or the agent prompt |
972e4fe to
d7d0096
Compare
There was a problem hiding this comment.
getFlashTransitionColor and getFullFadeTransitionColor are refactors and not a merge.
It is the better solution in this case to reduce the number of guards needed.
It's good enough for me, but xezon may want to have the refactor in its own commit, to keep the merge commit clean. I'll leave that up to him.
The rest looks good.
Yeah I figured that. But I wasn't 100% sure so I was just going to wait to see what he was going to say. |
|
There are more GameWindow related files, for example GameWindowID, GameWindowGlobal |
d7d0096 to
f707fd7
Compare
|
This merges the shared game window implementation and moves it into Core:
AnimateWindowManager.hAnimateWindowManager.cppGameWindowID.hGameWindowManager.hGameWindowManager.cppGameWindowManagerScript.cppGameWindowTransitionsStyles.cppBefore this change, Generals and Zero Hour differed by product-name banners, a documentation typo, two Zero Hour WND parsing additions, and game-specific transition colors.
Generals gets
ON_MOUSE_DOWNWND status.Refactoring
Verification