View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0007165 | MMW v4 | Other | public | 2011-01-12 11:03 | 2011-02-18 05:21 |
| Reporter | Ludek | Assigned To | |||
| Priority | urgent | Severity | minor | Reproducibility | always |
| Status | closed | Resolution | fixed | ||
| Product Version | 4.0 | ||||
| Target Version | 4.0 | Fixed in Version | 4.0 | ||
| Summary | 0007165: Hide self-defined media server(s) | ||||
| Description | All media applications like WMP, tVersity, XBMC, TM hides self-defined media shares/servers. i.e. you cannot browse tVersity media server by using same instance of tVersity. I think that MediaMonkey should behave same way. | ||||
| Tags | todoc-help | ||||
| Fixed in build | 1344 | ||||
|
|
Fixed in build 1344 |
|
|
Verified in 1344, but this probably is a bad idea during testing of MM4. Users no can't confirm if the MediaMonkey server is functioning as expected or not. You can only see it on other devices which makes testing and confirming problems harder. |
|
|
Reminder sent to: jiri, rusty I agree on this with Lowlander for now it is useful to be able to test MM Media servers within MediaMonkey without need to go to other PC and start MediaMonkey to test MediaMonkey MediaServer Functionality, but I also Agree with Ludek that this should be fixed for MM 4.0 Final version. |
|
|
I think that it's necessary to test MM UPnP functionality mostly from other applications anyway. So, yes, it might be useful to keep this enabled for testing purposes, but it might give users/scripters incorrect impression that this will always be the case. |
|
|
For this purposes and for DUnit testing there is a trick: If you set port = 4000 then you will see the server in MM interface ;-) |
|
|
Verified 1344 Along with Regression testing on port 4000 |
