Posted by member 71746 on 2003-11-16 14:26:16
So here's a new one for ya's:
I've got some scripting set up to handle hotspots.. in the !BarShow bang, I've defined !HotspotOFF BarTabHS and in !BarHide I've defined !HotspotON BarTabHS
When the !BarShow is called, the hotspot is successfully disabled. When the !BarHide is called, the hotspot remains inactive. That's weird.
Here's where it gets weirder.
Using !.exe, I can call !HotspotON BarTabHS and nothing happens, but as soon as I call !HotspotOFF for *ANY* of the other hotspots that are defined, the BarTabHS becomes active!
This wouldn't be weird if any of the other hotspots had territorial disputes with the BarTabHS, but all the other hotspots are nowhere near the BarTabHS. Furthermore, in the !BarHide bang, all the other hotspots are disabled with !HotspotOFF commands before the !HotspotON BarTabHS is called as the last instruction in the script.
Ain't that just messed right up! :D
I've got some scripting set up to handle hotspots.. in the !BarShow bang, I've defined !HotspotOFF BarTabHS and in !BarHide I've defined !HotspotON BarTabHS
When the !BarShow is called, the hotspot is successfully disabled. When the !BarHide is called, the hotspot remains inactive. That's weird.
Here's where it gets weirder.
Using !.exe, I can call !HotspotON BarTabHS and nothing happens, but as soon as I call !HotspotOFF for *ANY* of the other hotspots that are defined, the BarTabHS becomes active!
This wouldn't be weird if any of the other hotspots had territorial disputes with the BarTabHS, but all the other hotspots are nowhere near the BarTabHS. Furthermore, in the !BarHide bang, all the other hotspots are disabled with !HotspotOFF commands before the !HotspotON BarTabHS is called as the last instruction in the script.
Ain't that just messed right up! :D