Phosphor
Qt6 / Wayland library suite for window-management tools
Loading...
Searching...
No Matches
PhosphorAnimationLayer Namespace Reference

Classes

class  SurfaceAnimator
 Concrete PhosphorLayer::ISurfaceAnimator driving show/hide via phosphor-animation Profiles. More...

Functions

PHOSPHORANIMATION_EXPORT void applyEffectStaticConfig (PhosphorRendering::ShaderEffect *shaderItem, const PhosphorAnimationShaders::AnimationShaderEffect &effect, const QStringList &shaderIncludePaths)
 Apply an animation pack's per-effect static configuration (fragment / vertex source, param preamble, entry scaffold, include paths, multipass buffers, wallpaper, depth) to a shader item.

Function Documentation

◆ applyEffectStaticConfig()

PHOSPHORANIMATION_EXPORT void PhosphorAnimationLayer::applyEffectStaticConfig ( PhosphorRendering::ShaderEffect * shaderItem,
const PhosphorAnimationShaders::AnimationShaderEffect & effect,
const QStringList & shaderIncludePaths )

Apply an animation pack's per-effect static configuration (fragment / vertex source, param preamble, entry scaffold, include paths, multipass buffers, wallpaper, depth) to a shader item.

This is the SAME code every production shader leg runs (SurfaceAnimator's attach and reuse paths both call it), exported so a preview host can configure a shader item exactly the way a real leg would. A preview that assembled its own static config would drift from the thing it claims to predict. Idempotent — every ShaderEffect setter no-ops on identity — and always-set: a repeat call after a metadata hot-reload propagates disabled features (multipass, wallpaper, depth) onto a reused item instead of leaving stale state.

Per-leg state — iTime, isReversed, translated parameters, geometry, the uniform extension — is NOT this function's concern; the caller threads those through separately, as the animator does.