update reading and writing rdl files to allow binding to named outputs #300

Activity

1. pramsey1234

   added this to Multi-output shaderson Sep 21, 2026
2. pramsey1234

   converted this from a draft issue on Sep 23, 2026
3. pramsey1234

   marked this as blocked by 2 issues on Sep 23, 2026

   • Update SceneObject to allow binding to a named output #298
   • Update SceneClass to allow a list of outputs #297
4. pramsey1234

   marked this as blocking on Sep 23, 2026

   • Overview of multi-output shader work #296
5. pramsey1234

   moved this from Planning to Ready in Multi-output shaderson Sep 24, 2026
6. pramsey1234

   marked this as blocking on Oct 6, 2026

   • Remove SceneObject::getBinding() functions which don't fetch output for the binding #320
7. pramsey1234

   self-assigned this

   on Oct 9, 2026
8. pramsey1234 commented on Oct 9, 2026

   

   pramsey1234

   on Oct 9, 2026

   Last edited by pramsey1234

   Author

   More actions

   I've started looking at this and it's less obvious than I expected how to extend the rdla syntax for optionally naming an output to bind to. Currently bind() can be:

   bind(shaderObject)
   or
   bind(shaderObject, value)

   If the output was unconditional then I would expect the arguments to change to

   bind(shaderObject, output)
   or
   bind(shaderObject, output, value)

   but if the output is optional then I'm not sure how to distinguish between

   bind(shaderObject, output)
   and
   bind(shaderObject, value)

   since both value and output can be a string
9. pramsey1234

   moved this from In progress to Ready in Multi-output shaderson Oct 13, 2026