Re: [mh] help with debugging an mh scene

[Gregg L. <gr...@li...>]

Marc MERLIN wrote:

> BTW, that mbr_lamp2_kpls scene looks a lot like a surrogate scene and I can
> tie it just like one, except I don't have the surrogate keyword, so what's
> the difference between the 2?

Let's see what a surrogate does using your prior example--only this time 
w/ the surrogate attribute:

IPLL, 09.94.25:08, lvr_kpl_mbr_lamp2, lvr_kplH|buttons,	PLM
IPLL, PLM:43, mbr_lamp2_kpls, kpl_tie_scenes, PLM
SCENE_MEMBER, lvr_kpl_mbr_lamp2, mbr_lamp1_kpls, surrogate

Now, some would argue that mbr_lamp2_kpls is something that they'd 
rather not mess with.  After all, it only exists so as to turn on 
lvr_kpl_mbr_lamp2's lamp.  Usually, I use the "hidden" group to keep 
these "annoying surrogate" items out of sight.  For example:

IPLL, PLM:43, mbr_lamp2_kpls, hidden, PLM

Ok.  So, now mbr_lamp2_kpls won't show up in certain web pages and now 
makes me happy.  So, what--right?  Well, some users (including myself at 
times) would prefer to simply set the "real" lamp, like:

$lvr_kpl_mbr_lamp2->set(ON);

You can't do that unless you use the surrogate attribute which 
"associates" the PLM controlled scene w/ the device.  You see, the above 
set doesn't set $lvr_kpl_mbr but instead looks for it's surrogate and 
sets it.  Of course, you can always set the surrogate:

$mpr_lamp2_kpls->set(ON):

regardless of whether you use the surrogate attribute or not.  It's 
really just a matter of preference/style.  Now, in your case of using 
multi-button-PLM scenes, the use of surrogate is pointless.  It's only 
when you're using a single PLM scene to control a single button that it 
makes sense.

Clear as surrogate mud?

Gregg