home *** CD-ROM | disk | FTP | other *** search
- > Why does ximap bother to have a message number
- >map at all? If you keep a pointer to the elt
- >instead (being sure to lock it!) that's all you
- >need. The elt will always have the correct message
- >number for that message, or 0 if it has been
- >expunged (in which case the elt becomes a zombie
- >elt).
-
- In order to use the X athena widgets Kevin Brock modified the Xaw list widget,
- and also created a special "browser" widget so things like double-click and
- SHIFT-select could be handled. Ximap or the newer Xlview call the browser
- widget routines. This latter widget uses a map which requires the message
- number as one of its elements to build the list widget's own map which demands
- message number like indices.
-
- I believe the "browser" widget could be rewritten to use the pointer to the
- elt, and then a special call could be made to update after an expunge which
- would nuke the zombies from the list, and redisplay the browser.
-
- All in all, such a rewrite is not worth the pain. When this code breaks it
- usually causes a crash in the bowels of xlib somewhere. We haven't had such a
- crash in a long, long time and so I think you can understand our hesitancy
-
- A better choice would be to one day abandon the Xaw's. A good job for a student
- ;-).
-
- Read windows do use the elt, and thus cope well with expunging.
-
- Bill
-
-
-
-
-
-
-