Prioritize explicit PI ref over PHOTON_INHERIT #164

Activity

1. noble-ux

   added

   bugSomething's broken that shouldn't be.Something's broken that shouldn't be.

   on Aug 27, 2020
2. JoshPiper commented on Aug 28, 2020

   

   JoshPiper

   on Aug 28, 2020

   Member

   More actions

   Not a bug? Intended behaviour is to leave blank with those.
   Registered PI isn't indexed by model, so that can't be used automatically pulled.
3. noble-ux

   added

   enhancementAn improvement to an already existing featureAn improvement to an already existing feature

   and removed

   bugSomething's broken that shouldn't be.Something's broken that shouldn't be.

   on Aug 28, 2020
4. noble-ux commented on Aug 28, 2020

   

   noble-ux

   on Aug 28, 2020

   MemberAuthor

   More actions

   We can move it around so
   explicit PI ref (table or name) > default > inherit

   Partial documentation issue, but ideally PI lighting would always be set to on when a model with a referenced PI is being used.
5. noble-ux

   changed the title [-]PHOTON_INHERIT pulls an empty config[/-] [+]Prioritize explicit PI ref over PHOTON_INHERIT[/+] on Aug 28, 2020
6. JoshPiper

   added a commit that references this issue on Aug 18, 2026

   fix: Prioritize explicit PI ref over PHOTON_INHERIT (#256)

   ...

   This issue will close once commit 4c9ac79 is merged into the 'development' branch.

   4c9ac79
7. JoshPiper

   closed this as completedin #256on Aug 18, 2026