Normal
[USER=114299]@breese[/USER] FreakyJ is reusing lots of code from MPExt so I assume that the getservicedescription message is hard coded right now. I'm not sure what you can test if not being a developer that want to test that the methods here:https://github.com/FreakyJ/MediaPortal-2/blob/FEAT_WifiRemoteForMP2/MediaPortal/Incubator/MP2Extended/ResourceAccess/MediaAccessServiceHandler.csgive what is needed for the existing clients.Basically we try to get the same clients that work with MP1 and MPExt to work with MP2Ext and MP2.
[USER=114299]@breese[/USER] FreakyJ is reusing lots of code from MPExt so I assume that the getservicedescription message is hard coded right now. I'm not sure what you can test if not being a developer that want to test that the methods here:
https://github.com/FreakyJ/MediaPortal-2/blob/FEAT_WifiRemoteForMP2/MediaPortal/Incubator/MP2Extended/ResourceAccess/MediaAccessServiceHandler.cs
give what is needed for the existing clients.
Basically we try to get the same clients that work with MP1 and MPExt to work with MP2Ext and MP2.