you have 2 possibilities 1. write your own gadget popup trigger control (i have it like this, quite nicely enhanced compared to system one...tooltips etc.)
2. use FntCharsInWidth to find how long text will fit to trigger bounds, cut text to make it fit, and use cut text with popup trigger not original one. Luc Le Blanc wrote: > So far, my impression has been that selector triggers > will grow as long as their text is, while popup triggers > are more tamed, staying within their set width. But I > hit a surprising result linking a popup trigger to a > list drawn with a call back proc. In this case, when I > receive a popSelectEvent, I call CtlSetLabel with the > selected line text, but then, the popup trigger will > extend as long as the text is, overwriting other form > objects. Is there a way to prevent this other than > maintaining a static truncated version of the line text? > > Any background info welcome. > > > Luc Le Blanc > -- For information on using the ACCESS Developer Forums, or to unsubscribe, please see http://www.access-company.com/developers/forums/
