I'm mostly posting these here so I don't forget. (And yes it is a critical issue!)
1)Screen Saver will override the GUI (Not so good as it bypasses some code flow)
2)Screen Saver 100% CPU issue.
3)Add "ss_enable=1" to the config file.
Printable View
I'm mostly posting these here so I don't forget. (And yes it is a critical issue!)
1)Screen Saver will override the GUI (Not so good as it bypasses some code flow)
2)Screen Saver 100% CPU issue.
3)Add "ss_enable=1" to the config file.
All three should be fixed now. Let me know if they are not.
You sure can! (Matrix screensaver that is - pressing F9 should still toggle it on/off even if it is disabled otherwise).
You've always been able to disable it. Go to Misc > Screen Saver... and set "Run After" to "Never."
Just wish I'd have known sooner.
14
Oh well, no big deal. I haven't got a crash from the latest revision yet. That's the important part. Moving to quarantined. [edit] or not. :P
I wonder if the problems could have something to do with having buttons mapped to Ctrl, Alt, and Shift. Allegro doesn't treat those as keypresses on their own, but ZC has code that specifically checks for them.
Scripts might also be a factor. I don't recall this ever coming up in 2.10, and that may well be why. The input variables interact directly with the internal control arrays. I've found that if I run this script:
If A is assigned to Alt, I can press it repeatedly or hold it and it won't stop the screensaver from starting. If it's another button, keypressed() still returns true, so input_idle() behaves as expected. I've seen some other weirdness, but I haven't been able to make it hang.Code:global script UnpressA
{
void run()
{
while(true)
{
Link->InputA=false;
Link->PressA=false;
Waitframe();
}
}
}
I'll try having input_idle check key[] rather than ZC's regular controller functions. I'm not sure that'll fix it, but it can't hurt.