Prety sure this can be done with any window that has a Settings button. Unlike bags which create multiple instances from a template file, I think the Settings window works like the quanitity selector. Only 1 instance can be open at a time and the window knows what called it. If true, this means the window can be taregeted and will function so long as its opened through a standard settings button.
Basiclly this is what the script would have to do:
Parent.Settings.Press = true
Parent.Parent.SetingsWindow.FarmeAndTitleMenu.SelectedIndex = menu item number
Parent.Parent.SettingsWindow.OKbutton.Press = true
Note: You'll have to figure out the correct item names and paths but this should work. All the script is really doing is activating existing controls. Since the SettingsWindow is being opened by the standard settings button, the relationship bettwen the 2 windows should be managed properly by the client.
|