The UK Home Automation Archive

Archive Home
Group Home
Search Archive


Advanced Search

The UKHA-ARCHIVE IS CEASING OPERATIONS 31 DEC 2024


[Message Prev][Message Next][Thread Prev][Thread Next][Message Index][Thread Index]

Audio Control schema changes


  • Subject: Audio Control schema changes
  • From: Stuart Booth
  • Date: Sat, 14 Feb 2004 15:16:00 +0000

Edward,

In your Audio Control schema <waves at Mark> revisions you suggested
changing the playlist edits to send out an event message that just
contains a Playlist.Info message block. This combines several
parameters into the one block:

Playlist.Info
{
Tracks="length of play list"
Index="index of current track"
Shuffle=[On  Off]
Repeat=[Stop  Track  Playlist]
}

So, say I send a playlist shuffle command:

Playlist.Shuffle
{
Shuffle=[On  Off]
}

I would then get back a Playlist.Info event message. But the Event
doesn't actually tell me what specifically has just changed. I'd need
to store the previous state to be able to detect this.

Generally I've preferred to send back the same command as the event
when it is actioned (which makes it dead easy to code too!).

At regular-ish intervals the Playlist.Info should then be sent out
combining all relevant known parameters into one information update.

That's how it works for Class=xAP-Audio.Transport[.Event] so I wonder
if this is an inconsistency?

S
--
Stuart Booth <<a
href="/group/xAP_developer/post?postID=JOG0aS1XmgEl-14786_-JizS-R1uO08NlPM1qiMeDFl8pylmQ6oYROPOt6sPdbmduAs2wOvXwPtlXAd1SC6ZQonl">stuart@x...</a>>
xAPFramework.net - a xAP software development framework for .net

<a href="http://www.xapautomation.org/";>http://www.xapautomation.org/</a>
<a href="http://www.xapframework.net/";>http://www.xapframework.net/</a>





xAP_Development Main Index | xAP_Development Thread Index | xAP_Development Home | Archives Home

Comments to the Webmaster are always welcomed, please use this contact form . Note that as this site is a mailing list archive, the Webmaster has no control over the contents of the messages. Comments about message content should be directed to the relevant mailing list.