To use scripting in NetStumbler, you should be fluent in a scripting language that supports Active Scripting on the Windows platform. Examples of such languages are VBScript and JScript, which are available on most Windows platforms; others you might consider are PerlScript and Python, available from ActiveState.
None.
This is called when the user requests that scanning be started.
None.
This is called when the user requests that scanning be stopped.
This is called when all of the results from the current scan have been processed.
This is called just after the application has received all scan results. It is called once for each item that was found. Since this is called frequently while scanning, the script should not perform complex operations that might take a long time to complete.
None.
This is called just before the application initiates a scan.
None.
This is called when the GPS is not responding, most typically because it is unplugged or configured incorrectly. For most GPS protocols, this will be called once every few seconds.
None.
This is called when the GPS indicates that it is unable to provide a position fix. Usually this is caused by poor satellite visibility.
This is called when the GPS indicates the current position.
This is called when the GPS indicates the current speed.
Called while scanning only when the IP address is reported to be changed. The IP address reported is the first one on the currently scanning adapter. NOTE: There are a number of cases where this function will get called but the IP address has not really changed - for example, the address changed on another adapter, or the IP routing or DNS information changed.
Called to indicate that NetStumbler has changed its location information for a BSSID.
NOTE: A BSSID's location is currently determined to be the location where the strongest signal was seen, which is almost never the actual location. It is likely that a future version of NetStumbler will perform some postprocessing on results, which will make it possible for OnPositionChange to be called long after the BSSID was seen, unlike the current behavior.
In addition to the standard runtime provided by the scripting host, the application makes some additional functions available for use by scripts.
Adds a custom item to the popup context menu for all networks. If the user selects this menu item, the named callback in the script is called with the BSSID and SSID of the network.
Let us suppose you have custom VBScript that contains the following:
Sub LaserCallback (bssid, ssid) If Robot Is Nothing Then Set Robot = CreateObject("Skynet.T9000") Robot.PointLaserAt(bssid) Robot.Say "Hasta la vista, " & ssid Robot.FireLaser End Sub AddItemContextMenu "LaserCallback", "Fire Laser"
The last line of code registers the callback with NetStumbler. After this executes, every network's context menu will include an item labelled "Fire Laser". When selected, this menu item will cause the network's BSSID and SSID to be passed to "LaserCallback", which executes the custom code shown.
Boolean value indicating whether the operation succeeded. True indicates success, False indicates failure.
Plays the requested sound file.
Internally, this calls the Win32 PlaySound API function with hModule = Null and fdwSound = SND_ASYNC | SND_NODEFAULT.
Boolean value indicating whether the operation succeeded. True indicates success, False indicates failure.
Plays the requested sound file repeatedly. To stop playback, call the function again, passing an empty string.
Internally, this calls the Win32 PlaySound API function with hModule = Null and fdwSound = SND_ASYNC | SND_NODEFAULT | SND_LOOP.