Under Windows 10, when Einstein@home runs as a screensaver it causes a problem (after exiting the screensaver) with the Scrivener authoring tool. Specifically, the system's cursor no longer "sees" Scrivener on the screen. If you click on the Scrivener window, whatever window is on the desktop *underneath* Scrivener gets the focus. However, clicking on the Scrivener icon in the task bar gives Scrivener the focus and the program is fully functional as long as all operations are done through the keyboard and not the mouse/cursor. No other programs are affected. I have reported this bug to Scrivener as well.
Copyright © 2024 Einstein@Home. All rights reserved.
Have you tried switching the
)
Have you tried switching the screen saver to a different one to see if the problem persists?
Yes. Switch the screensaver,
)
Yes. Switch the screensaver, restart Scrivener, and the problem does not recur. Switch back, and the problem recurs after the screensaver is invoked.
FWIW the problem isn't BOINC, since I ran SETI@home for years with no problem.
Brad Kalbfeld wrote: Yes.
)
So you are saying it's the Einstein screensaver? It's under construction and there's a thread for that that you may wish to contribute to so they can figure out what the problem is.
Another thing to think about is that any screensaver requires cpu cycles to run meaning Boinc runs slower and less efficiently. It could also slow down whatever you are doing with Scrivener.
mikey wrote:So you are saying
)
The original screensaver here at Einstein is NOT under construction, it's been around for many many years and that is the only one distributed via Boinc.
What the thread is about, is that if anyone like to develop/program their own screensaver then there is a foundation to do so and if you're willing to share and the result is better than the original then the project might incorporate it as the new standard.
Holmis wrote: mikey wrote:So
)
I apologize for misunderstanding the intent of the thread over there!