It appears to be an issue with the current version in place, but in our development version (the next release version) it's not an issue. It's a big update when we do roll it out, so I cannot promise when we will get it rolled out but I know it has to happen by the end of the 2nd quarter of 2015.