First of all, sorry for taking so much time to respond. We really appreciate your feedback! The latest build has this issue fixed.
