Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!wuarchive!decwrl!bacchus.pa.dec.com!shlump.nac.dec.com!clt!ferwerda
From: ferwerda@clt.enet.dec.com (Paul Ferwerda)
Newsgroups: comp.windows.x.motif
Subject: Tab Group Question
Message-ID: <1990Oct30.144937@clt.enet.dec.com>
Date: 30 Oct 90 19:49:37 GMT
Sender: news@shlump.nac.dec.com
Reply-To: ferwerda@clt.enet.dec.com (Paul Ferwerda)
Organization: Digital Equipment Corporation, Nashua, New Hampshire
Lines: 40

--
>> If so, why would anyone need to add
>> an item to the tab group using XmAddTabGroup()?
>
>If writing an application in 1.1, one wouldn't.


I've got a layout widget that is subclassed off of XmManager.

 LayoutWidget "DayDisplay"
	LayoutWidget "ScrollWindow"
		XmScrollBar
		DayslotsWidget (private manager widget)
			TimeslotWidget (private manager widget)
				XmText
	TimbarWidget (private manager widget)
	XmPushButton
	XmPushButton
	XmPushButton

If I don't do any XmAddTabGroup(s) then only the XmScrollBar ends up
traversable (other than the Text widget).  Should my LayoutWidget be
doing something special in order to have the PushButtons be
traversable?  If I do an explicit XmAddTabGroup for each PushButton
they become traversable but that results in another problem (doing a
menupopdown moves the keyboard focus to the next traversable widget,
ie keyboard focus is on PushButton#1, I F10 or click on the menubar,
then click on the title and PushButton#2 gets the keyboard focus. (Ugh).

Paul

---
Paul		EASYNET=> loptsn::ferwerda
Gordon		UUCP=> decwrl!clt.enet.dec.com!ferwerda
Loptson		DARPA Internet=> ferwerda%clt.enet.dec.com        
Ferwerda	Tel (603) 881 2221