|
a/doc/upmpdcli.html |
|
b/doc/upmpdcli.html |
|
... |
|
... |
| 881 |
<td align="left" valign="top"><p class="table">Path to icon to be displayed by control point. <a href="#upmpdcli.iconpathnote">See note</a></p></td>
|
881 |
<td align="left" valign="top"><p class="table">Path to icon to be displayed by control point. <a href="#upmpdcli.iconpathnote">See note</a></p></td>
|
| 882 |
<td align="left" valign="top"><p class="table"></p></td>
|
882 |
<td align="left" valign="top"><p class="table"></p></td>
|
| 883 |
<td align="left" valign="top"><p class="table"></p></td>
|
883 |
<td align="left" valign="top"><p class="table"></p></td>
|
| 884 |
<td align="left" valign="top"><p class="table">iconpath</p></td>
|
884 |
<td align="left" valign="top"><p class="table">iconpath</p></td>
|
| 885 |
</tr>
|
885 |
</tr>
|
|
|
886 |
<tr>
|
|
|
887 |
<td align="left" valign="top"><p class="table">Path to HTML file to be used as presentation
|
|
|
888 |
page. <a href="#upmpdcli.presentationnote">See note</a></p></td>
|
|
|
889 |
<td align="left" valign="top"><p class="table"></p></td>
|
|
|
890 |
<td align="left" valign="top"><p class="table"></p></td>
|
|
|
891 |
<td align="left" valign="top"><p class="table">presentationhtml</p></td>
|
|
|
892 |
</tr>
|
| 886 |
</tbody>
|
893 |
</tbody>
|
| 887 |
</table>
|
894 |
</table>
|
| 888 |
</div>
|
895 |
</div>
|
| 889 |
<div class="paragraph" id="upmpdcli.iconpathnote"><p><strong>iconpath</strong> note: the UPnP protocol has provisions for a renderer to send
|
896 |
<div class="paragraph" id="upmpdcli.iconpathnote"><p><strong>iconpath</strong> note: the UPnP protocol has provisions for a renderer to send
|
| 890 |
the URL to a descriptive icon as part of the device description. The icon
|
897 |
the URL to a descriptive icon as part of the device description. The icon
|
| 891 |
to use can be set using the <strong>iconpath</strong> configuration file parameter. Due to
|
898 |
to use can be set using the <strong>iconpath</strong> configuration file parameter. Due to
|
| 892 |
current (and probably permanent) <strong>upmpdcli</strong> limitations, the image file
|
899 |
current (and probably permanent) <strong>upmpdcli</strong> limitations, the image file
|
| 893 |
<strong>must</strong> be a 64x64 32 bits-per-pixel png file.</p></div>
|
900 |
<strong>must</strong> be a 64x64 32 bits-per-pixel png file.</p></div>
|
|
|
901 |
<div class="paragraph" id="upmpdcli.presentationnote"><p><strong>presentationhtml</strong> note: the file referenced by the path will only be read
|
|
|
902 |
once when upmpdcli starts, it can’t presently be used for status updates
|
|
|
903 |
(but I guess that you could put a redirect in there, to something more
|
|
|
904 |
dynamic served by a real HTTP server).</p></div>
|
| 894 |
</div>
|
905 |
</div>
|
| 895 |
</div>
|
906 |
</div>
|
| 896 |
<div class="sect1">
|
907 |
<div class="sect1">
|
| 897 |
<h2 id="upmpdcli.openhome">OpenHome ohMedia services</h2>
|
908 |
<h2 id="upmpdcli.openhome">OpenHome ohMedia services</h2>
|
| 898 |
<div class="sectionbody">
|
909 |
<div class="sectionbody">
|
|
... |
|
... |
| 962 |
</div>
|
973 |
</div>
|
| 963 |
</div>
|
974 |
</div>
|
| 964 |
<div id="footnotes"><hr /></div>
|
975 |
<div id="footnotes"><hr /></div>
|
| 965 |
<div id="footer">
|
976 |
<div id="footer">
|
| 966 |
<div id="footer-text">
|
977 |
<div id="footer-text">
|
| 967 |
Last updated 2015-02-03 23:29:39 CET
|
978 |
Last updated 2015-04-26 10:02:19 CEST
|
| 968 |
</div>
|
979 |
</div>
|
| 969 |
</div>
|
980 |
</div>
|
| 970 |
</body>
|
981 |
</body>
|
| 971 |
</html>
|
982 |
</html>
|