mirror of
https://github.com/brues-code/ClassicAPI.git
synced 2026-11-16 16:10:36 +00:00
frame:SetMouseClickEnabled / SetMouseMotionEnabled / IsMouseClickEnabled / IsMouseMotionEnabled and SetPropagateMouseClicks / CanPropagateMouseClicks, with enableMouseClicks, enableMouseMotion and propagateMouseInput="Clicks" in XML. Retail (probed on 5.5.4) routes the two separately: motion goes to the top motion-enabled frame, a press to the top click-enabled frame, so a click on a motion-only frame reaches the frame under it and a click-only frame takes clicks without ever taking the motion. A frame that propagates clicks passes the press on; each gets it and then the release, top-first. The engine's one mouse bit stays "click or motion"; Frame::MouseInput keeps the frames with one half off. The focus pass's probe call skips frames with motion off. The press handler's focus read becomes the click walk, which is that same read while no frame uses the split or click propagation; the press and release dispatches run each extra target's button slot after the engine's. EnableMouse sets both halves. IsMouseEnabled is both halves and still answers 1 or nil as the engine does: pfUI compares it with SpellIsTargeting.