- Joined
- Mar 26, 2007
- Messages
- 7,920
I just had another extremely frustrating experience trying to stop MapFinder while it was generating Large maps.
1) I carefully pressed CTRL-ATL-G once. MapFinder just kept going.
2) Repeat step 1 precisely 3 times!
3) I carefully pressed CTRL-ATL-G once. Great! MapFinder says it just stopped; NO, its running again!
4) I carefully pressed CTRL-ATL-G once. MapFinder just kept going.
5) I carefully pressed CTRL-ATL-G once. MapFinder stopped; Thank you Merlin!
It seemed impossible that MapFinder recognized a single hot key sequence as both a start and stop event in step 3 above; it appears that the key code repeat feature is being triggered! The number of milliseconds that a key is held down is configurable and quite often made very short by default.
I can think of no explanation of why 4 times out of 5 Map generations MapFinder did not detect even one CTRL-ATL-G hot key sequence when during each Map generation it was carefully, meticulously, purposefully, entered.
It is a very bad idea to use a hot key as a toggle for starting/stopping MapFinder, especially when the hot key will repeat when held down too long. Once the repeat key feature kicks in, it hard to ensure that an odd number of hot keys are sent.
Additional information about the above issue:
A) When the map was being generated, the screen would turn all white, and would return to normal after each new Map was generated; I've seen this before; it doesn't seem to affect the Maps generated by MapFinder and rebooting the machine always seemed to fix it; I imagine it was caused by a memory leak somewhere in the system, not necessary in either BtS or Buffy; just a visual artifact that seems to have no effect on functionality.
B) CTRL-ALT-O Map tab; delays were 0.00, 2.50 and 2.50.
I just verified that the hot key CTRL-ALT-G does indeed repeat when held down purposely long. It showed MapFinder stopped and presumably started (MapFinder should display something - its file parameters - when started) about 7-8 times and then BtS stopped responding to any input (keyboard or mouse) and had to be killed via task manager. The mouse pointer would blink every 20-30 seconds as though a Map was being generated, but otherwise the screen was frozen - never updated a pixel other than mouse cursor. I recall seeing the task "not responding" as well.
Sun Tzu Wu
1) I carefully pressed CTRL-ATL-G once. MapFinder just kept going.
2) Repeat step 1 precisely 3 times!
3) I carefully pressed CTRL-ATL-G once. Great! MapFinder says it just stopped; NO, its running again!
4) I carefully pressed CTRL-ATL-G once. MapFinder just kept going.
5) I carefully pressed CTRL-ATL-G once. MapFinder stopped; Thank you Merlin!
It seemed impossible that MapFinder recognized a single hot key sequence as both a start and stop event in step 3 above; it appears that the key code repeat feature is being triggered! The number of milliseconds that a key is held down is configurable and quite often made very short by default.
I can think of no explanation of why 4 times out of 5 Map generations MapFinder did not detect even one CTRL-ATL-G hot key sequence when during each Map generation it was carefully, meticulously, purposefully, entered.
It is a very bad idea to use a hot key as a toggle for starting/stopping MapFinder, especially when the hot key will repeat when held down too long. Once the repeat key feature kicks in, it hard to ensure that an odd number of hot keys are sent.
Additional information about the above issue:
A) When the map was being generated, the screen would turn all white, and would return to normal after each new Map was generated; I've seen this before; it doesn't seem to affect the Maps generated by MapFinder and rebooting the machine always seemed to fix it; I imagine it was caused by a memory leak somewhere in the system, not necessary in either BtS or Buffy; just a visual artifact that seems to have no effect on functionality.
B) CTRL-ALT-O Map tab; delays were 0.00, 2.50 and 2.50.
I just verified that the hot key CTRL-ALT-G does indeed repeat when held down purposely long. It showed MapFinder stopped and presumably started (MapFinder should display something - its file parameters - when started) about 7-8 times and then BtS stopped responding to any input (keyboard or mouse) and had to be killed via task manager. The mouse pointer would blink every 20-30 seconds as though a Map was being generated, but otherwise the screen was frozen - never updated a pixel other than mouse cursor. I recall seeing the task "not responding" as well.
Sun Tzu Wu