theWord

chr0naut wrote: ↑Thu Feb 06, 2025 11:30 pm I can confirm that as of 7 February 2025, with the latest updates to Windows Defender on Windows 11, the executable is still being quarantined/removed.

I just tried myself with 2/7/2025 version and it still will not detect a trojan, strange.
Anyone else that can provide feedback?

Costas

Just for a test, I downloaded 1515 and Defender deleted it, makes me wonder why this "virus" has just been found??? Myself and others have submitted the specific version (1527) to Microsoft. It may be that they didn't really 'fix' their invalid detection, they just added an exception for ...

On Jan 28, 2025, Microsoft Defender started identifying the file theword.exe as a threat containing a Trojan. By default, and without asking the user, Microsoft Defender removed the file theword.exe (actually put it in Quarantine ) which is the main executable of the theWord Bible Software. Practica...

Hi Willem, that would be almost impossible to do within theWord itself since it does not support alternate v11n schemes. We do have several utilities that we use to map different v11n schemes, but in the end theWord itself will only understand the KJV one. So a technical solution for this should be ...

rdwray wrote: ↑Tue Oct 11, 2022 4:10 pm What about the difference between "Bible Search" and "Book Search" windows?

was unable to reproduce in high-dpi, although i can see in the code why this can be problematic.

rdwray wrote: ↑Tue Oct 11, 2022 12:56 am The "Verse:" combo text box follows Windows 11 settings, is there another way to change the text color?

Screenshot 2022-10-10 175317.jpg

fixed in beta 1530

I assume that the version label gets hidden because of the high-dpi settings and the auto-resizing of the dialog.
I will see if I can fix that, it is important.

rdwray wrote: ↑Tue Oct 11, 2022 5:14 pm Just one thing, the "Help > About" does not show the version and I use a link that opens a generic "theWord.exe" without the version number.

Can I have a screenshot of this one pls?

Can you pls try the latest beta? I have disable the high-dpi compatibility
Costas

Yes this is it. I don't have an idea to be honest.
The 10-12% cpu shows that something is looping there, but I can't imagine what that might be.

Do you have any other tools to troubleshoot this? I don't know wine to be honest.
Costas

Can you try to get the latest beta and try this? In the latest beta i have reverted the high-dpi support in the manifest.

Yes it will.
THere are a couple of issues (like high-dpi compatibility) that I would like to change before activating the auto-update
Costas

Hi All,
thanks for the valuable feedback. I think I am going to put out a new minor update so these dpi settings become the default behavior of theWord, as it seems that many users have this issue.
Costas

I dislike that too, I am with you.
Unfortunately it's not that simple. The delay is not due to disk/memory, has to do with the layout sub-system being used.
And it's hard to change.
Costas

Thank you for bringing this to my attention, we' ll check it.