Re: XEmacs has just (more than) doubled in size

Andy> In fact I'm still pretty convinced that the expose events Andy> are for the widget being *unmapped* rather than mapped. In X11, an unmapped window can't receive events at all because it's invisible. If all of the descendents of the subwindow/glyph are mapped first, then the subwindow/glyph is mapped, it cannot step on its own toes (unless that causes its children to reconfigure themselves). I guess it's possible that since tabs are normally used in dialog boxes, the programmer got away with an implicit assumption that the tab control widget would always be on top, and wouldn't have to deal much with Expose events. I'm becoming rapidly convinced this is the way to go. I got a < 1 sec flash where I saw the tabs completely discombobulated, in no particular order, not in a row (maybe about three rows?) Can't reproduce, of course :-( -- University of Tsukuba Tennodai 1-1-1 Tsukuba 305-8573 JAPAN Institute of Policy and Planning Sciences Tel/fax: +81 (298) 53-5091 __________________________________________________________________________ __________________________________________________________________________ What are those two straight lines for? "Free software rules."