Auto-Generated Interface questions

[DaveB]

Another observation - The tile template seems to be one to one only. You can not re-use a template for another overlay or it will not generate. Each additional overlay must have a unique tile template.

Each add on tile must have its' own unique tile template in order to generate. If you make up one general template for tiles and then attempt to re-use it for multiple tiles, only one tile gets generated.

I think that was what you were questioning below.

[Dean Roddey]

Yeh, that's because the output tile name is based on the input tile. So each time it gets generated, it overwrites the previous one.

[DaveB]

You can just drag the tiles screen up and down to get to all the tiles. The Hue stuff is disabled of course if you select a light that isn't color enabled. It would look kind of empty if we just removed them. Also, any room could have a color enabled light, even if it was added after the fact, since a room isn't limited to only its own lights.

Yea - Got it. Concerning the lights, The scene would look out of balance.

[DaveB]

Sorry - But as I pick through this, I am finding some additional small items.

The Now Playing Scene - I am using iTunes

Transport controls are not working
Volume control is not working

Transport and volume work fine on the home scene.

[Dean Roddey]

OK, I'll check that. When you say not working, do you mean don't do anything or give an error? If you look at the commands, do they look correct? Are they for the right driver and using the right field?

[DaveB]

Art comes up as does all the metadata. The buttons and slider are pointed at the correct player. The button does not press and there is no error generated. It almost seems like there is an overlay on top of the buttons and slider, making them inaccessible. Actually, the static image widget is getting stacked on top. I think that is the issue.

[Dean Roddey]

Oh, it's because it thinks the 'power' is off. Initially when I added the Power class to those guys, I didn't have the ones that really are doing faux power initially set their power state to true. If you go to the field browser and write True to the Power field of the renderer, then it'll start working. Those guys user a state to disable them if the power isn't on.

That's something that needs to be addressed. Things have to be powered on now, but we want to do it generically. But, what I want to do is update the auto-gen to allow you to provide some setup without having to do a global action (unless you just want to do one.) I.e. let you choose the devices to power on, the switchers to switch, the volumes to set, upon entry.

In the current code those that don't really need powering up (the ones faking Power) will initialize themselves to look like they are already powered on when they start. And, until I get the above done, that will make it work like it did before.

[DaveB]

That fixed the issue.

I need to integrate my autopatch with these scenes via globals I guess. It really gets deeper than that as I first need to select the source (4 available ) then turn on the zone
I actually have started to integrate squeeze into the interface and will change everything from iTunes.
Do you know what is left to do on the v2 squeeze driver?

[DaveB]

Dean - You should add a progress bar under the artwork on the now playing scene and for now, just add a power button to the scene.

[Dean Roddey]

There will already be a power button if you are set the appropriate global action. You can set one for music and movies for power off and on. If one of them is defined, the button for that action shows up.