flan/examples/core-input-mouse.flan
Joseph Ferano 49ec1651ae raylib enum keywords carry their enum's prefix
Key members are :key-r, :key-space, :key-left-shift; MouseButton members
are :mouse-left through :mouse-back — mouse- over button- because gamepads
have buttons too. Bare members collided across enums and with user code.

The bindings enum directive grew an optional third column declaring the
Flan-side member prefix, stripped before the C prefix is applied, so key-r
checks against KEY_R rather than KEY_KEY_R; a member that does not carry
the declared prefix is reported, not checked under a guessed name. The
enum-member error grew a did-you-mean: one edit away, or the bare name of
a prefixed member, so :r suggests :key-r.

sand.flan is the author's live WIP and is deliberately not touched; its
three keywords (lines 161-166) leave test_session and sand-headless red
until he moves them. Everything else that calls the two enums moved.
2026-09-20 21:49:11 +07:00

61 lines
2.5 KiB
Plaintext

;;;; raylib [core] example - input mouse
;;;;
;;;; examples/core/core_input_mouse.c. Needed three new bindings — show-cursor,
;;;; hide-cursor and cursor-hidden? — which are now in vendor/raylib.
;;;;
;;;; The C's `else if` chain over the seven mouse buttons is a `cond` here.
;;;; That is not a workaround: `cond` is what Flan has and it is the same
;;;; first-match-wins shape, with `:else` where C falls off the end. The order
;;;; matters in both — two buttons pressed on the same frame give the earlier
;;;; one, which is the C's behaviour and not an accident of the port.
;;;;
;;;; The colour has to be a `defvar` rather than a `let`, for the reason
;;;; core-input-keys' position does: it is state between frames.
(import rl "vendor:raylib")
(defconst screen-width 800)
(defconst screen-height 450)
(defvar ball-color rl/Color)
(defn main [] ()
(rl/init-window screen-width screen-height
"raylib [core] example - input mouse")
(defer (rl/close-window))
;; The C also initialises the ball's POSITION, to {-100,-100} so it starts
;; off-screen. That is dead there and is not here: the first thing the loop
;; does is overwrite it with get-mouse-position, before anything is drawn.
(set ball-color rl/darkblue)
(rl/set-target-fps 60)
(until (rl/window-should-close?)
;; Update
(when (rl/key-pressed? :key-h)
(if (rl/cursor-hidden?) (rl/show-cursor) (rl/hide-cursor)))
(let [ball (rl/get-mouse-position)]
(set ball-color
(cond
(rl/mouse-button-pressed? :mouse-left) rl/maroon
(rl/mouse-button-pressed? :mouse-middle) rl/lime
(rl/mouse-button-pressed? :mouse-right) rl/darkblue
(rl/mouse-button-pressed? :mouse-side) rl/purple
(rl/mouse-button-pressed? :mouse-extra) rl/yellow
(rl/mouse-button-pressed? :mouse-forward) rl/orange
(rl/mouse-button-pressed? :mouse-back) rl/beige
:else ball-color))
;; Draw
(rl/with-drawing
(rl/clear-background rl/raywhite)
(rl/draw-circle-v ball 40.0 ball-color)
(rl/draw-text "move ball with mouse and click mouse button to change color"
10 10 20 rl/darkgray)
(rl/draw-text "Press 'H' to toggle cursor visibility" 10 30 20 rl/darkgray)
(if (rl/cursor-hidden?)
(rl/draw-text "CURSOR HIDDEN" 20 60 20 rl/red)
(rl/draw-text "CURSOR VISIBLE" 20 60 20 rl/lime))))))