Doh! Nasty bug in jsiPodFetch


    The last release wasn’t thoroughly tested and this morning I found a nasty bug that prevents the application to start on its first run.

    That is a god way to get rid of users, isn’t it?

    I added code in the last release to check for the device name of the player. That way the application can find the player even if the drive letter is changed. If that happens I replace the last drive letter with the current drive letter in the player path setting. The problem is that there is no player path on the first run so I get an ‘index out of range’ exception early in the application.

    It is fixed now so I will do a new release tonight or tomorrow. It will probably not be tested enough either, but at least it should not piss of new users.