suggestion log file viewer
Posted: 30 Jun 2012 03:03
The logfileviewer (which I guess is new? anyway, I just about now dicovered it and already fell in love with it) can't open a logfile of a playlist that is currently playing. I do understand that this is probably due to "open files" or something and I don't have a problem with this. But I can imagine two things:
a) Not all users might be aware of this file access collision and might be wondering "is this broken?"
b) This might become an issue when running long playlists or random / scripted playlists and using a non-date/time-based naming convention. Something "stupid" like "we are using one and only logfile for everything". Of course every user is entitled to her own stupid ideas still user might desire to open the playlist regardless of playstate...
My suggestion is: a logfile that is currently "in use" should be marked as "you can't touch this now because it is in use". This prevents confusion. Further, I could imagine the system offering to open a temporary copy of said logfile which would probably be good enough to solve the aforementioned "b)" scenario.
a) Not all users might be aware of this file access collision and might be wondering "is this broken?"
b) This might become an issue when running long playlists or random / scripted playlists and using a non-date/time-based naming convention. Something "stupid" like "we are using one and only logfile for everything". Of course every user is entitled to her own stupid ideas still user might desire to open the playlist regardless of playstate...
My suggestion is: a logfile that is currently "in use" should be marked as "you can't touch this now because it is in use". This prevents confusion. Further, I could imagine the system offering to open a temporary copy of said logfile which would probably be good enough to solve the aforementioned "b)" scenario.