00007: double-clicking state files can result in weird "after#xxxx" errors

« 00006 | Issues | 00008 »

Summary: double-clicking state files can result in weird "after#xxxx" errors

Created: 2007–03–27 10:21

Status: Released

Category: Bug

From: frankie

Version: 1.0

Released_In: 2.0

Description:
Sometimes double-clicking a state file to load results in a file load error “after#xxxx” or something similar.

---

Comments

Possible workaround: usually clicking the file to select it and then clicking “Open” seems to work. —frankie

NOTE: We haven't seen this issue in a while, so the issue may have silently gone away. It's possible it may be specific to a certain OS. If you encounter this issue, please document it here including what OS, EDGE version, 'uname -a' output, etc. If we don't see it for some time, we may close the issue unexplained. — frankie June 27, 2007, at 11:21 AM

Closed the issue as unexplained. Please let us know if anyone sees this error. — admin October 09, 2007, at 02:16 PM

Opening this issue back up again. I am sometimes seeing this now when saving states (as opposed to opening them), and the filename is coming out with weird "after#" filenames. — frankie January 14, 2008, at 04:38 PM

frankie January 29, 2008, at 02:52 PM: We think we have this fixed now. Let us know if anyone sees any funny errors or filenames with "after#xxxx" in the name.

---

« 00006 | Issues | 00008 »

Associated Commits

| commit | eaa84fd5a85a3b80b6c5a096e43cea7c9dd07f57 link6 | || | Author: | Frank Graffagnino | | Date: | Tue Jan 29 14:51:36 2008 -0600 | | Message: | [@Issue 00007: Update tcl event logic Updated the event handling logic a bit so that "after" calls and timer events don't interfere with the result string when loading and saving states. @] |

Affected Files:

plugin_Linux_FC3/dsp_state.so | Bin 84051 -> 93005 bytes
 1 file changed, 0 insertions(+), 0 deletions(-)