I would love to be able to click the filename provided under “path” in the detail window that pops up when you click an episode’s name. It would make it so much easier to enqueue freshly-downloaded episodes in my media player of choice, rather than having to navigate manually through the filesystem.
(Yes, I know there are media management solutions which don’t require navigating manually to the file, but that’s how I do it for now.)
Unfortunately, something like this is not easily achievable, Chrome and FF don’t allow you to open links to the file system in Windows Explorer and links to a media player would require a media player prefix, which means the OS your accessing the drone UI from needs to be configured to handle that and drone would need to handle it for your media player of choice.
There are too many variables to make this reliable, so we will not be investing time into solving it. This is likely something that a browser plugin would be great for.
Not to mention that a link to /volume1/video/series/Drama/Breaking Bad/Season 01/1x01 - Pilot.mkv would not do me any good on my Windows PC. Drone would then also need to know that I’ve mapped /volume1/video on a virtual V: drive. Seems like a lot more trouble than it’s worth.
Well, that’s disappointing, but thanks for the explanation.
As regards NMe, not every feature needs to be useful to every user. However, if you’re storing your shows on a network resource and have it shared out (as I’m sure many of us do) then that resource will be available via UNC. This is how I had to configure my download directory in NZBDrone anyway, so the link would be useful to me across any of my network devices.
I agree that not every feature needs to be useful to every user, but if this feature were to be built, I’d get an error every time i accidentally click the link. I would know why I’d get that error and wouldn’t care much about it but the average user would not understand. Confusion is a bad thing for any application, which is why I like how intent markus101 and Taloth are on keeping it simple.
the interface is clearly communicating with the background service, why can’t you have that open the file?
That only works if you’re access the UI from the same machine that drone is running on, which isn’t always the case and I’d suspect is often not the case. I don’t think that would work if its running as a Windows service (because there is no user interaction). Non-Windows would be another problem altogether. I’d say the percentage when this would work would be low enough and the actual use of it would be even lower. Still not worth the time/complexity.