janssen@parc.xerox.com (Bill Janssen) (01/31/91)
I've been thinking that ATK would be much nicer with other non-ATK ICCCM-complient applications if selections were promoted to be system-wide concepts, rather than left to the druthers of the individual view implementors. This would mean, for instance, that every view would have the notion of a PrimarySelection and SecondarySelection, and have methods to access them, and would notify im when they changed. Thus selecting something in textview could cause notification of the selection in X, by going through im and xim, and other applications, both ATK and non-ATK, could access that selection. This would require adding some code and methods to view, and to im, and to xim, but could be done in a backwards-compatible fashion. This would make a number of inter-client concepts (particularly my favorite, shift-select) much easier to implement in ATK. Comments? Bill