> Bernie wrote: >> Good question. In general, if you know which toolbox you want to >> use, you've probably got a good idea where it's defined. If you >> know the toolbox but don't know where it's defined, you could key >> in the function name into an editor window and cmd-double-click >> it. The FB header file will (usually) be opened. >> >> Unfortunately, FB's headers are an untidy mess with stuff >> scattered all over the show, but here are a few clues: >> - If you're working with nibs, you should include Tlbx >> IBCarbonRuntime.incl >> - Calls beginning "HIView" require Tlbx HIView.incl >> - Carbon events need Tlbx CarbonEvents.incl (Note: Tlbx >> HIView.incl header also includes Tlbx CarbonEvents.incl, so if >> you're using HIViews, you don't need to include both.) >> - Some weird menu functions such as CopyMenuItemTextAsCFString >> will probably be defined in Tlbx Menus.incl >> - Control manipulation functions such as GetControlPopupMenuHandle >> will be in Tlbx Controls.incl... but, hang about!, Tlbx >> Controls.incl doesn't exist... so a good bet would be Tlbx >> ControlDefinitions.incl On Jan 19, 2008, at 11:31 AM, Bob Krueger wrote: >>> My problem is that I don't know what toolbox to use. For some things the best solution is RTM. Brian S.