Xiphos STRING bug about xiphos HOT 6 CLOSED

i've implemented a fix (workaround) which i will push when i again have a non-firewalled environment, in about 5 days -- i'm out of the country right now and my network access is restricted.
i hope to put out a new xiphos release relatively soon.

that said, i am thoroughly mystified as to how you managed to trip that particular instance -- those color selections are among the earliest items to be set during initialization. do you have an old ".xiphos" directory lying around, with a questionable or dodgy settings.xml?

from xiphos.

It may have been a security update from Microsoft that triggered it.

I set up a user to run without Administrator privileges. If I run Xiphos using Runas Administrator, the problem disappears. If I run Xiphos as a non Admin, it repeatedly causes the same error without fail..

Most Windows 10 users are running as Administrator. I don't. Microsoft says it's better to run as non Admin. Like Linux. Windows lets you run things but warns an Administrator when he is taking action that requires Administrative access.

from xiphos.

i suspect that what's happened to you is that settings.xml was detected but found unreadable because the non-admin user has inadequate privs.

if you nuke your old .xiphos directory and start again, or copy its content in a read/writable manner, or just alter its privileged access, i suspect it will work. that said, the workaround is suitable anyhow, and has just been pushed.

from xiphos.

from xiphos.

the Sword directory contains module content for any app, not xiphos' specific data, like settings.xml.

i had thought that, running with reduced privs as a non-admin, general (esp. write) access to files like .xiphos/settings.xml would be insufficient. perhaps not; i'm not a windows guy at all.

from xiphos.

from xiphos.