flan/examples/core-input-mouse.flan
Joseph Ferano a4c6b996ff def re-runs its initialiser, and defvar is renamed defonce
The trio the author decided on 2026-09-20 is now all built: def is CL's
defparameter — its initialiser runs on every daemon re-run, unguarded, so
an edited initialiser repaints the same storage on C-c C-c plus re-run —
defonce (Clojure's name for CL's defvar, per the author) initialises once
behind the .init~once. flag, and defconst stays the image.

One parse arm reads both forms; the difference is Ast.reinit, carried to
Tast.global's grerun. Emit.startup_plan gives a def no guard flag, and
Check.check_global lifts every def initialiser — zero and literal
included — into global/<n>, so the host's startup reaches it through the
function cell and a re-evaluated def swaps it (Session's def_inits;
Emit.redefinition declares the cell for a non-sibling target). The old
defvar spelling is refused with the rename and both compiling spellings,
and every program, test, doc and editor list is swept — except sand.flan,
the author's live WIP, whose seven defvar lines are flagged in FIX.org
and keep its three dependent tests red on this branch.
2026-09-21 07:12:04 +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 `defonce` 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)
(defonce 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))))))