The update to correct this was posted today, Feb. 4th, at about 2:45 PST.  I was on the phone with them yesterday for several hours.  Charles finally got it and sent the problem to their development team.  This morning I got an email that is was corrected.