maybe if you included a little Delay ? right before the Error ? or something maybe things are happening too fast at an inhuman rate and therefore unexpectedly ? some how the code is expecting to have a human response time amount of time left to get it's thing done but in this case it does not . maybe . just a wild shot in the dark
what i am trying to do is have an isTesting mode that cuts the GUI out of the picture and just returns to the rest of it whatever the GUI would have returned assuming the GUI is correct . but it seems a bit extra . so far . is this what they call amock ? i don't know . so the GUI never actually opens on screen is the idea . you never send the >>show.. Message or something
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 296 |
Nodes: | 16 (2 / 14) |
Uptime: | 72:33:21 |
Calls: | 6,657 |
Calls today: | 3 |
Files: | 12,203 |
Messages: | 5,332,304 |
Posted today: | 1 |