Staz, I think these may be already on your list, but if not, would you please consider adding them? (These are for _after_ your vacation and some other higher-priority items.) 1. I think the MOST useful addition you could make to the editor would be a popup menu in the header area to show all the FNs in the current project that call the current FN (shown in the header). If a selection is made from the menu, a window would be opened or scrolled to the first line in that FN where it is called, and the FN name selected so cmd-H could be used to find subsequent calls in the same FN 2. It would be enormously helpful for FIND to change the header in each found window to show the name of the function where the target was found (just as it shows the FN of the cursor location when in the window). This would avoid repeated clicks between windows to find out what FN that is. 3. If a window _opened_by_ FIND has never become the active (front) window, I think FIND should close it before opening the next file to search. I don't know how difficult this would be--maybe it would be better to say if the window isn't dirty--but it would sure cut down on the litter of windows that weren't the one you were looking for. I can't think af any real advantage to having them left open. 4. There should be a way for the debugger to access the area where register vars are stored when a new FN is called, or to keep its own record of register values, so when you click one of the calling FNs in the FN Stack window, the true variable values from that FN can be displayed instead of the current (new) register values. Thanks, 0"0 =J= a y "