This posting is older than 6 months and can contain outdated information.
I see your point and fragility certainly is an issue with GUI scripting.
However, I guess it would better cope with updated software than strict Behavior rules do. You may check that with different versions of e.g. Powerpoint. Unlike BCK, it is supposed to adapt to the latest version's GUI anyway.
Keeping BCK separate from the user interface should be optional:
I would say that for debugging purposes a direct dig into the BCK hierarchy would be more preferable than isolation.
So: a practical combination of both worlds...
(see various comments on Versiontracker on RemoteBuddy and competition)
Implementing 2 simple interface commands would provide scripters the essential hooks to RB:
1. ShowMenu(list,insertlocation) -> Passing a list {"option 1","option 2","option 3"} somewhere in the RB menu hierarchy to display it onscreen.
2. DidSelect(menu x, item y) -> returning selected option back to the calling AppleScript.
This way, it's up to the scripter to intercept GUI anomalies.
Last edited: 04.09.2006 23:53:46
