Hey Adrian, 2009/6/23 Adrian Sutherland <[email protected]> > > Would it be a good idea to add a setTabIndex() to form (or > Interactive? - not sure where in the object model) Widgets?
I think we should just take WWidget, as also WAnchor and WPushButton can get a tabindex. It is quite harmless if you define a tabindex to a widget that does not support it (and also quite bizarre). > Not only would this be good for accessibility, but it would also allow > some fine tuning of the tab order, if a field is tabable (i.e. -1 to > disable). You are probably right that it should be added. I would prefer the Qt style WWidget::setTabOrder(WWidget *first, WWidget *second) over a setTabIndex(int) method though as it does not get confused by other widgets present in the page ? Regards, koen ------------------------------------------------------------------------------ Are you an open source citizen? Join us for the Open Source Bridge conference! Portland, OR, June 17-19. Two days of sessions, one day of unconference: $250. Need another reason to go? 24-hour hacker lounge. Register today! http://ad.doubleclick.net/clk;215844324;13503038;v?http://opensourcebridge.org _______________________________________________ witty-interest mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/witty-interest
