GUI script freeze when minimize client
| Case number: | 845829-989215 |
| Topic: | Crash/Hang |
| Opened by: | Rav3n_pl |
| Status: | Ongoing |
| Assigned: | tamirh |
| Priority: | 3 |
| Type: | Bug |
| Opened on: | Monday, January 31, 2011 - 19:15 |
| Last modified: | Wednesday, September 19, 2012 - 23:19 |
OS: Windows XP SP3
When I run any GUI script it freezes between commands: I need to restore window for a moment to continue script.
I knowh, but cant run GUI recipes in background because of that behavior.
| Priority: 3 » 1-High |
Shameless bump.
It should work normally when client is minimized.
425 is very specific and we need use GUI scripts for it.
I have a feeling I know the cause for this.
Sound effects seem to be queued in a buffer. When I minimize my client for an hour or two at work and then restore, often times I have to wait a few minutes for all the "Pop-pop-pop-pop-pop!" sounds to complete playing all-at-once.
The easy fix would be to disable sound effects, or sound effect queueing (or something!), when the window is minimized.
Shameless BUMP!
Because of planning GUI comeback it NEED to be FIXED.
Who said the GUI was planning a comeback ?
| Assigned: Anonymous » tamirh |
I know, right?
Last I heard: the Selection Interface was making a comeback! ;-)
We'll keep you posted well ahead of time if anything does make a comeback (such as the sliders, for example) to make sure the important and relevant feedbacks get bumped (and finally addressed!) ahead of time.
| Assigned: Anonymous » tamirh |
I'll look into it, but because it's a GUI script issue, it's not a very high priority.
see http://fold.it/portal/node/987007 for some additional infos
| Status: Open » Ongoing |
| Priority: 1-High » 3 |
I've added a temporary fix for this that will go out in the next devprev.
It adds a windows-only option which lets you continue running Foldit in the background, GUI macros and all. Because this runs everything when Foldit is minimized some people may not want this.
The full fix would be to move the GUI script execution off onto a separate thread. That's a low priority now though.
![](http://128.95.1.228:8000/tracking_pixel.gif?events=scAdd&f=1111&wdata={"x":12, "y":11}){kind=tracking}
That's normal. It's always done that.