Technical diary

HUD redesign - large headline text, split lines, date/time, non-GAAD guard

The on-screen HUD is redesigned for both views: (1) The view name ('Design Generator' / 'Design Evolution') displays at size 30 as a large headline. (2) In the Design Evolution view, the generation count moves to its own line below the headline. (3) A date/time line (e.g. '25 Jun 2026 09:03') is added to both views. (4) A guard is added so the HUD never draws in blank or non-GAAD Blender files - it exits immediately unless the scene is named 'GAAD Generator' or 'GAAD Design Evolution', or contains a GAAD collection.

Panel Scripts box shows all four scripts; scenes named GAAD Generator / GAAD Design Evolution

Two related naming/panel changes: (1) The Scripts box in the GAAD panel now shows all four script filenames - Generator, Tree, Report, and Add-on. Previously the add-on was omitted. (2) The two Blender scenes are given explicit names: the generator/breeding world is named 'GAAD Generator' (set on first build by the generator script); the lineage tree scene is named 'GAAD Design Evolution' (set by the tree script). These names drive the HUD is_tree detection and all scene-switching logic in the addon.

Fix: double-draw HUD handler on addon reload

The _gaad_hud_add() function now always calls _gaad_hud_remove() before registering a new draw handler. Previously, the module-level _gaad_hud_handle variable would reset to None on addon reload while the old handler remained active, causing a second handler to be registered and the logo/text to draw twice. The fix ensures only one handler is ever active.

Double HUD traced to handler re-registration on addon reload

After installing updated addon versions, the HUD was drawing twice - two logos and two sets of text stacking on screen. Initially suspected to be two addon versions installed simultaneously, but the real cause was that Blender resets module-level variables (including _gaad_hud_handle) on addon reload without calling unregister(), so the 'if handle is None' guard failed and a second draw handler was registered on top of the still-active first one.