Trevor Arjeski <tmarjeski@gmail.com> writes:

Here is a patch to resolve this issue: