Feature request: clear cache on next restart

[haggis999]

(06-10-2013 20:32)winxi Wrote:  MinimServer and MinimWatch aren't completely different applications. MinimServer consists on the one hand of the UPnP server application and on the other hand of a frontend which allows to control this UPnP server application (i.e. the minim icon or the console on headless machines). MinimWatch provides just the frontend to remotely control instances of the UPnP server application on other machines in the LAN. I personally consider this to be quite a clever concept.

MinimServer and MinimWatch are, of course, very closely related and the functionality this combination provides is unquestionably clever. However, just as with my television, I continue to think of the remote control as being a separate beast from the thing being controlled - but I can't get too excited about this matter. It is only a minor issue.

Quote:Your suggestion to change the icons from MinimWatch would allow to distinguish between an icon generated by MinimWatch for instances on other machines and an icon generated by MinimServer on the same machine.

The primary advantage of this as I see it would be to emphasise that local and remote instances behave in different ways, with a key difference being that the default file location for settings such as writeAllTags is on another machine for MinimWatch.

Quote:However, it would not allow to distinguish between two instances running on other machines. The unique distinction is provided by the tool tip text for the icon. Maybe it would be a good idea to add the displayName also to the top of the icons context menu to make the distinction more obvious.

I have just found that changing the displayName setting on MinimWatch does not change the associated tooltip. It only changes the name of the related MinimServer instance as shown by a control point such as BubbleUPnP. What you actually get as a tooltip for MinimWatch is just the default value of 'MinimServer[<Host name>]'

David